oh yeah, perfectly straightforward, only took several thousand words to confusingly explain.
Nope, not simple. Yep, this is a git usability problem.
In the ruby/github world, people generally violate this and DO rewrite 'public' history in order to get 'cleanness', primarily because almost ALL history is 'public', since you tend to show people work in progress on github, or just push it there to have a reliable copy in the cloud. And yes, this sometimes leads to madness.
Comments
oh yeah, perfectly straightforward, only took several thousand words to confusingly explain.
Nope, not simple. Yep, this is a git usability problem.
In the ruby/github world, people generally violate this and DO rewrite 'public' history in order to get 'cleanness', primarily because almost ALL history is 'public', since you tend to show people work in progress on github, or just push it there to have a reliable copy in the cloud. And yes, this sometimes leads to madness.