Messages in this thread | | | Subject | Re: Is there an recommended way to refer to bitkeepr commits? | From | Rob Landley <> | Date | Thu, 11 May 2017 11:12:17 -0500 |
| |
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
| |