From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752165AbdEMJf7 (ORCPT <rfc822;w@1wt.eu>);
        Sat, 13 May 2017 05:35:59 -0400
Received: from Galois.linutronix.de ([146.0.238.70]:55844 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751380AbdEMJf5 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 13 May 2017 05:35:57 -0400
Date: Sat, 13 May 2017 11:35:26 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
cc: Rob Landley <rob@landley.net>, Michael Ellerman <mpe@ellerman.id.au>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Al Viro <viro@zeniv.linux.org.uk>, Oleg Nesterov <oleg@redhat.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Is there an recommended way to refer to bitkeepr commits?
In-Reply-To: <87tw4ptmzj.fsf@xmission.com>
Message-ID: <alpine.DEB.2.20.1705130930200.2836@nanos>
References: <87k25ol41u.fsf@xmission.com> <CA+55aFxj4Oe8+DbNLzk+SKoW99MTeF+m1SAiC4hgW=bN2dpvEQ@mail.gmail.com> <87h90rj2ub.fsf@concordia.ellerman.id.au> <1de8bc32-ebac-141a-080a-ef1c5a149904@landley.net> <87r2zuc08d.fsf@concordia.ellerman.id.au>
 <alpine.DEB.2.20.1705120941060.1800@nanos> <87shka2kxn.fsf@xmission.com> <1638b34f-742d-d718-6ab2-cfed861278e4@landley.net> <87tw4ptmzj.fsf@xmission.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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