4 ms·
>It is just such a common complaint, and I have yet to hear of any down side that actually makes sense to me as someone who has a fair understanding of git Pro
by seclorum 15y ago
>It is just such a common complaint, and I have yet to hear of any down side that actually makes sense to me as someone who has a fair understanding of git
Probably because gaining a fair understanding of git is damned hard. Why you want to do things, and what these actions are actually for is not clear from the topology of the terms that git uses to describe these actions.
- mattbriggs 15y agoFair enough, git does have a hellish interface. That is a great complaint, and I totally agree with it. The "zomg history editing!" thing just doesn't seem to die though, even though git been out for quite awhile now, and has become quite popular
- seclorum 15y agoI think complaints about history editing have some validity - as a team leader, I definitely do not want the history of my project, warts and all, to be editable by junior members attempting to hide mistakes/flaws in the production flow. This leads to cacophony when time comes to figure out why things went wrong, if they do, somewhere in the past.
- rlpb 15y agoThis is not what rebase is for. As a team leader, nobody can rewrite the history of your project but you.