2 ms·
Agreed. Honestly, I see the appeal of maintaining a clean history, but shouldn't that be done in some non-destructive fashion? Do we need source-control on ou
by Pxtl 13y ago
Agreed. Honestly, I see the appeal of maintaining a clean history, but shouldn't that be done in some non-destructive fashion? Do we need source-control on our source-control? Or at least simply flag squashed commits instead of destroying them?
- Mindless2112 13y ago> Do we need source-control on our source-control? That's more or less what Mercurial's changeset evolution [1] is/will be (it's not enabled by default yet). [1] http://mercurial.selenic.com/wiki/ChangesetEvolution http://mercurial.selenic.com/wiki/ChangesetEvolution
- jlgreco 13y ago> I see the appeal of maintaining a clean history, but shouldn't that be done in some non-destructive fashion? Don't rebase code that is public (few people recommend that you do) and there is nothing destructive about it. When I rebase my changes before making them public, I am not destroying history, I am deciding history.