3 ms·
> I have to admit I’ve never understood the point of keeping the history linear. Bisect, blame, and log, among other features, are all easier to use with a lin
by dahart 5y ago
> I have to admit I’ve never understood the point of keeping the history linear.
Bisect, blame, and log, among other features, are all easier to use with a linear history. They’re not unusable with non-linear / many branches, just easier linear.
I’m not quite sure I understand your comment though - it implies that you consider linear history to be a strange and/or non-default thing to do. What’s the implied point of not keeping the history linear, or what is your preferred workflow? I’m not entirely sure what’s being compared, but linear is the default you get from more than 1 commit. Linear is very natural with a team of one or only a very small number of people. Linear is a lot nicer than branchy for branches that have exactly 1 commit.
- elsjaako 5y agoOk, that makes sense. > I’m not quite sure I understand your comment though - it implies that you consider linear history to be a strange and/or non-default thing to do. Sometimes you get a branch, I get them even on personal projects if I forget to push and work on a different computer. I've heard people say that, when they do get a branch, they will rebase to make the history linear instead of having a merge. I don't think that is default.