Re: Is there an recommended way to refer to bitkeepr commits?

Thomas Gleixner
2017-05-13T09:35:59Z

On Fri, 12 May 2017, Eric W. Biederman wrote:
> Which leaves me perplexed. The hashes from tglx's current tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
> on kernel.org and the hashes in your full history tree differ.
> Given that they are in theory the same tree this distrubs me.
>
> Case in point in the commit connected to:
> "[PATCH] linux-2.5.66-signal-cleanup.patch"
> in tglx's tree is: da334d91ff7001d234863fc7692de1ff90bed57a

That's the proper sha1 for my tree. I jsut verified it against the original
tree which I still have in my archive.

> *scratches my head*
>
> Something appears to have changed somewhere.

Correct. That full history git rewrote the commits in my bitkeeper import.

history.git:

commit 7a2deb32924142696b8174cdf9b38cd72a11fc96
Author: Linus Torvalds <torvalds@athlon.transmeta.com>
Date: Mon Feb 4 17:40:40 2002 -0800

Import changeset

full-history:

commit 26245c315da55330cb25dbfdd80be62db41dedb2
Author: linus1 <torvalds@athlon.transmeta.com>
Date: Thu Jan 4 12:00:00 2001 -0600

Import changeset

and as a consequence all other commits have different shas as well.

Sigh....

Thanks,

tglx