3 ms·
Inline branching would be nice... I think they do away with this for simplicity. Inline branching doesn't make that much conceptual sense a lot of the time. Th
by jmtulloss 19y ago
Inline branching would be nice...
I think they do away with this for simplicity. Inline branching doesn't make that much conceptual sense a lot of the time. That said, I wish Hg had it.
- KirinDave 19y agoForgive me, because this is not an insult, but this "doesn't make conceptual sense" argument I hear so much is so much nonsense and excuses to me. Git supports multiple workflows and allows you to either directly resolve tainted-working-copy situations directly or avoid them. By allowing for local branches you enable multiple parallel lines of development in one repository. It saves space, it saves effort, it saves time, and it's a cleaner way to organize your projects (all in one place rather than scatted across a directory listing). It also means you can evade the tainted-working-copy problem entirely by keeping short-lived, private, parallel branches of current feature development. Personally, I much prefer this mode of operation when I have the foresight to do it.
- silentbicycle 18y agoIncidentally, Mercurial does this now too. (for the archives)