From: Michael Ellerman <mpe@ellerman.id.au>
To: Rob Landley <rob@landley.net>,
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: Fri, 12 May 2017 11:50:10 +1000 [thread overview]
Message-ID: <87r2zuc08d.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1de8bc32-ebac-141a-080a-ef1c5a149904@landley.net>
Rob Landley <rob@landley.net> writes:
> 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?
No you didn't forget, I see several:
refs/tags/v1.2.0
refs/tags/v2.6.0
refs/tags/v4.5-rc3
refs/tags/v2.4.0
refs/tags/v1.0.0
refs/tags/v2.2.0
refs/tags/v2.0.0
refs/tags/v4.5-rc4
refs/tags/v4.5-rc5
refs/tags/v4.5-rc2
refs/tags/v0.0.1
refs/tags/v4.5-rc1
But in the original mail Eric was wanting to refer to a specific
Bitkeeper revision using the BK revision id, eg:
Fixes: BKrev: 3e8e57a1JvR25MkFRNzoz85l2Gzccg ("[PATCH] linux-2.5.66-signal-cleanup.patch")
In your tree that is c3c107051660 ("[PATCH] linux-2.5.66-signal-cleanup.patch"),
but you don't have the 3e8e57a1JvR25MkFRNzoz85l2Gzccg revision recorded
anywhere that I can see.
cheers
next prev parent reply other threads:[~2017-05-12 1:50 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
2017-05-12 1:50 ` Michael Ellerman [this message]
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=87r2zuc08d.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rob@landley.net \
--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
Powered by JetHome