On Tuesday, 10 December 2013 at 13:43:51 UTC, Dicebot wrote:
It is not a problem to reset local branches on rare occasions
like this one, whatever developer count is. Reason why rebasing
of public branches is discouraged is not some abstract
inconvenience of collaboration - it is the fact that commit
hashes change in history and anything that has been pointing to
part of history that got rewritten will be broken (especially
important if, for example, commit hashes are embedded into
This collection of "anything" includes local tracking branches
people might already use, a simple "git pull" won't work anymore.
Thus, it's very much not just an abstract inconvenience – it
might be trivial to fix, but less Git-savy people might not
immediately know how to handle the situation.