[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h90rj2ub.fsf@concordia.ellerman.id.au>
Date: Thu, 11 May 2017 16:59:40 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Al Viro <viro@...iv.linux.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
Oleg Nesterov <oleg@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
rob@...dley.net
Subject: Re: Is there an recommended way to refer to bitkeepr commits?
Linus Torvalds <torvalds@...ux-foundation.org> writes:
> On Wed, May 10, 2017 at 3:04 PM, Eric W. Biederman
> <ebiederm@...ssion.com> wrote:
>>
>> Thomas Gleixner appears to have a tree with all of those same commits
>> except with the BKrev tags stripped out.
>
> That's the best import - so use that tree by Thomas, and just use the
> git revision numbers in it (and say "tglx's linux-history tree" or
> something).
I've been using this one by Rob Landley which seems good:
https://landley.net/kdocs/fullhist/
It's grafted into the modern history so you can search seamlessly
between the two which is pretty nice. I don't see any Bitkeeper tags
though.
cheers
Powered by blists - more mailing lists