From: Rob Landley <rob@landley.net>
To: Michael Ellerman <mpe@ellerman.id.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
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?
Date: Thu, 11 May 2017 11:12:17 -0500 [thread overview]
Message-ID: <1de8bc32-ebac-141a-080a-ef1c5a149904@landley.net> (raw)
In-Reply-To: <87h90rj2ub.fsf@concordia.ellerman.id.au>
On 05/11/2017 01:59 AM, Michael Ellerman wrote:
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>
>> On Wed, May 10, 2017 at 3:04 PM, Eric W. Biederman
>> <ebiederm@xmission.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.
I went through and found/tagged the major old releases, did I forget to
upload a new tarball after that?
v0.0.1 cff5a6fb66765e90470f4d9ca2398da0ca3c75d5
v1.0.0 a068026b4a060e822892a64d5107fb58c45743ef
v1.2.0 8610c92442d125f165dc84e4a96f5cbc9b240484
v2.0.0 a374953c636bd91ea40b2d1e31af5405b90e8bf8
v2.2.0 bf330b5e3c471d0b67737c4822b0174ef4f89bed
v2.4.0 13a80dffb74939e292b6e90e5d79dd26d577489f
v2.6.0 4e9b4bc7a660962ae5f04f939469263b91cf95c2
Rob
next prev parent reply other threads:[~2017-05-11 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 22:04 Eric W. Biederman
2017-05-11 0:47 ` Linus Torvalds
2017-05-11 6:59 ` Michael Ellerman
2017-05-11 16:12 ` Rob Landley [this message]
2017-05-12 1:50 ` Michael Ellerman
2017-05-12 7:43 ` Thomas Gleixner
2017-05-12 14:45 ` Eric W. Biederman
2017-05-12 16:30 ` Rob Landley
2017-05-12 17:49 ` Andreas Schwab
2017-05-13 17:26 ` Rob Landley
2017-05-13 19:38 ` Andreas Schwab
2017-05-13 4:11 ` Eric W. Biederman
2017-05-13 9:35 ` Thomas Gleixner
2017-05-13 17:17 ` Rob Landley
2017-05-12 16:46 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1de8bc32-ebac-141a-080a-ef1c5a149904@landley.net \
--to=rob@landley.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®