3 ms·
I avoid it because of complete lack of commit amendment tools. It seems like quarter of the time I make a commit I mess up either a commit message or a file li
by theamk 6y ago
I avoid it because of complete lack of commit amendment tools.
It seems like quarter of the time I make a commit I mess up either a commit message or a file list, and have to "git amend". I have no idea how the sqlite devs live without the feature, they must be much more careful programmers than I am.
- mscrnt 6y agoYou could always try "fossil amend" as a commit amendment tool for starters.
- rkeene2 6y agoThere has pretty much always been a way to amend commits -- the difference is in Fossil this amendment is done by writing a new journal entry (artifact) noting which commit is being amended and how, rather than modifying the commit directly. Generally, the compiled version (base+resultant set of amendments) is displayed to the user, but the entries which modified the commit are also available to be seen.
- everybodyknows 6y ago>modifying the commit directly. Git preserves a record of the origial commit, plus amendments leading up to the final - git-reflog. The reflog is however subject to periodic pruning by default - see git-gc.
- rkeene2 6y agoFossil preserves the journal of activities forever, and across clones.
- sgbeal 6y ago> I avoid it because of complete lack of commit amendment tools. That's downright wrong: https://fossil-scm.org/home/help/amend https://fossil-scm.org/home/help/amend