3 ms·

> I dont even get why people rebase for a merge. I never did this and I get the entire history not a distorted version of it. Except that the history is disorg

by u801e 7y ago

> I dont even get why people rebase for a merge. I never did this and I get the entire history not a distorted version of it. Except that the history is disorganized and is not organized into distinct patches that only do one thing where each patch has a well written commit message. People seem to want to treat the VCS as a back up system rather than a system to keep track of changes. Technically you could get the former by configuring your editor/IDE to generate a commit every time you save the file, but that in itself would lead to a very large history that wouldn't be useful (meaning commands like git blame would be next to useless).

giancarlostoro 7y ago
> Except that the history is disorganized and is not organized into distinct patches that only do one thing where each patch has a well written commit message. This seems like a separate problem... I know where commits come from cause the first thing I write on mine is the JIRA / Trac or other related ticket number / code. It is pretty obvious where a commit originated from if you do this. The rest is useful meaningful information. If somebody writes useless commit messages, that's on them and the rest of the team for letting them do so.