Quote:
Originally Posted by JSWolf
The problem with doing this via the code is that you'll have to do it every single time you update Calibre.
|
Wrong. Steps are as follows:
- Make changes.
- committing the change tracks it to preserve even after downloading other peoples' changes.
Code:
git commit --all --message="my changes/commit message"
- In future, update the source checkout with the rebase switch:
Either way, you'd have to pull the changes. Rebasing them preserves local commits, which is nicer than seeing a merge conflict. (Instant panic while people new to version control wonder what to do.)
@JSWolf, have you used version control before?
If not, remember that assumptions are not always wise.
If yes, why not give a fair explanation, rather than oversimplifying? How are people supposed to learn?
There are better reasons not to use the code... like using firewalls for what they are meant for.