4 ms·
imagine if you could express that 'rebase' commit as a summary commit, without destroying history and history, but allowing you to present the change as a docum
by convolvatron 10y ago
imagine if you could express that 'rebase' commit as a summary commit, without destroying history and history, but allowing you to present the change as a documented logical unit.
(i.e. what if git log just showed the highest level aggregate commit message by default)
commenting your changes properly doesn't have to involve destroying history - thats just an accidental failure of git that has caused a lot of people a lot of trouble
- WorldMaker 10y agoI do think it is a bit of a mistake for git UI tools to so prominently feature the DAG first instead of something more akin to `--first-parent` views. (Especially in the way that a lot of old SVN/CVS users came into git wanting a simple straight line view and finding tools like rebase instead of `git log --first-parent`, we've ended up in a bit of a mess where people expect to do the heavy lifting in "sandblaster" tools like rebase instead of better UI/UX tools.)