From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754820AbdEKG7s (ORCPT ); Thu, 11 May 2017 02:59:48 -0400 Received: from ozlabs.org ([103.22.144.67]:35457 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754731AbdEKG7o (ORCPT ); Thu, 11 May 2017 02:59:44 -0400 From: Michael Ellerman To: Linus Torvalds , "Eric W. Biederman" Cc: Al Viro , Thomas Gleixner , Oleg Nesterov , Linux Kernel Mailing List , rob@landley.net Subject: Re: Is there an recommended way to refer to bitkeepr commits? In-Reply-To: References: <87k25ol41u.fsf@xmission.com> User-Agent: Notmuch/0.21 (https://notmuchmail.org) Date: Thu, 11 May 2017 16:59:40 +1000 Message-ID: <87h90rj2ub.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Linus Torvalds writes: > On Wed, May 10, 2017 at 3:04 PM, Eric W. Biederman > 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