Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1640867
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Is there an recommended way to refer to bitkeepr commits? |
| Date | 2017-05-13 11:40 +0200 |
| Message-ID | <tGBGO-1O2-29@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <tG825-5LR-9@gated-at.bofh.it> <tGduN-1an-5@gated-at.bofh.it> <tGkcV-62A-3@gated-at.bofh.it> <tGlLI-7eN-9@gated-at.bofh.it> <tGwH7-70c-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Is there an recommended way to refer to bitkeepr commits? Michael Ellerman <mpe@ellerman.id.au> - 2017-05-12 04:00 +0200
Re: Is there an recommended way to refer to bitkeepr commits? Thomas Gleixner <tglx@linutronix.de> - 2017-05-12 09:50 +0200
Re: Is there an recommended way to refer to bitkeepr commits? ebiederm@xmission.com (Eric W. Biederman) - 2017-05-12 17:00 +0200
Re: Is there an recommended way to refer to bitkeepr commits? Rob Landley <rob@landley.net> - 2017-05-12 18:40 +0200
Re: Is there an recommended way to refer to bitkeepr commits? Andreas Schwab <schwab@linux-m68k.org> - 2017-05-12 19:50 +0200
Re: Is there an recommended way to refer to bitkeepr commits? Rob Landley <rob@landley.net> - 2017-05-13 19:30 +0200
Re: Is there an recommended way to refer to bitkeepr commits? Andreas Schwab <schwab@linux-m68k.org> - 2017-05-13 21:40 +0200
Re: Is there an recommended way to refer to bitkeepr commits? ebiederm@xmission.com (Eric W. Biederman) - 2017-05-13 06:20 +0200
Re: Is there an recommended way to refer to bitkeepr commits? Thomas Gleixner <tglx@linutronix.de> - 2017-05-13 11:40 +0200
Re: Is there an recommended way to refer to bitkeepr commits? Rob Landley <rob@landley.net> - 2017-05-13 19:20 +0200
Re: Is there an recommended way to refer to bitkeepr commits? Linus Torvalds <torvalds@linux-foundation.org> - 2017-05-12 18:50 +0200
csiph-web