On Sat, Aug 8, 2015 at 6:45 PM, Hannes Magnusson <[email protected] > wrote:
> On Sat, Aug 8, 2015 at 3:23 PM, Peter Cowburn <[email protected]> > wrote: > > > > > > > On 8 August 2015 at 23:07, Hannes Magnusson <[email protected]> > > wrote: > > > >> On Sat, Aug 8, 2015 at 10:47 AM, Paul Dragoonis <[email protected]> > >> wrote: > >> > >> > Umm - not quite sure what happened there - my git had a seizure - > >> > > >> > > >> > >> Do you have any idea what caused this? > > > > > > Paul rewrote his commit history (any commits he was author or committer) > > to use a consistent email address.See > > https://gist.github.com/dragoonis/5e3bcc657d481b5cdfc1 > > > > > >> It appears to have been a force push? > >> > > > > It must have been, to rewrite history like that. > > > > > >> > >> I'm wondering if we need to force-push latest known good copy of the > repo. > >> We can't allow over 2k commits that could be unclean like this. > > > > > > Before today, I thought that force push was restricted on our Git repos. > > However, that appears to be limited to php-src.git (any others?) at the > > moment. > > > > Could we at the very least put in the same restriction on all of our > > repos? We should make the barrier to being able to force push as high as > > possible! It's almost never the right thing to be doing for our project. > > > > > Gah. I thought so too and was wondering how this could have happened. > +1 on rejecting forced pushes. > > Definitely should not allow force-push in the future. > Does anyone have a reasonable recent clone that we can restore? > My local copy hasn't updated for ~2weeks so I'm unhelpful. > And sorry, my local copy is also very much outdated :/ > > -Hannes >
