Open krillin666 opened 1 year ago
At the moment can only leave a quick reply, but I think there are a few options (roughly from easiest/laziest to hardest but cleanest)
git checkout - b krillin666
). Then now and then run git fetch origin
and git merge origin/master
. You might need to resolve merge conflicts now and then, depending on how big are your changes. The downside is that your changes are a bit buried behind merge commits, so it might be hard to tell what are they actually (unless you diff
files directly)git rebase
-- not sure what are the best tutorials. The upside is that it would always be very clear what are your changes, and they will always be 'on top' of upstream HPI. The downside is that it has some learning curve, but it's quite a useful skill :)
Hi !
I've had some headaches sometimes updating both yours and @karlicoss HPI. Usually I delete the previous cloned HPI repo folders and then do the installation process outline in your README. But since I've made modifications to some modules, like the
signal.py
which wasn't working, I then have to manually change the python module files again.Is there any way I can only update both HPI and HPI-sean and leave user modifications intact ? Sorry, I'm a noob at git
Thanks!