[petsc-dev] Commit collision/corruption?

[Sean Farley]

Jed Brown writes:

> On Wed, Mar 6, 2013 at 5:10 PM, Sean Farley <sean at mcs.anl.gov> wrote:
>
>> Who did the rebasing? Which version of mercurial? Jed, was this
>> through your gitifyhg extension?
>>
>
> There was never any rebasing. Barry made the messed up commit over here.
>
> https://bitbucket.org/BarryFSmith/petsc-dev-simp/commits/de73c9a7d341d846b5e16a8d61a48242f0521c02
>
> It was rewritten on subsequent push (when gitifyhg applied the commit to my
> local hg) to only name the files that changed.

This right here is the most suspect part. The minute you start monkeying
around with private functions and whatnot, you are in the danger zone. I
will have a hard time believing this isn't a bug in gitifyhg. In fact, I
am willing to bet on it.