On 11.12.2013 11:36, Cox, Michael wrote:
On Tue, Dec 10, 2013 at 10:35 PM, Vladimir Prus
wrote: On 11.12.2013 09:25, Ahmed Charles wrote:
Unfortunately, as it stands, you seem willing to unilaterally and knowingly inconvenience everyone with a git clone of boost
I am not sure it's obvious, but git transition is not done. Anybody with a git clone of boost today shall expect much more entertainment than a need to 'git reset' a single module. And, BTW, technically I can rewrite the history without a single forced push.
How could rewriting the history be done without a forced push? Just so I can avoid accidentally doing that.
My understanding is that all git commits are cryptographically linked with the SHA numbers so that if you have a SHA number for a commit, you are guaranteed that commit and all the ones in its history are the same for you and any one else looking at them.
Just look at develop-rewritten branch in build repo - it is a history-rewritten version of 'develop', but no forced push is necessary - because it's another branch. - Volodya