From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757581AbdELHnu (ORCPT ); Fri, 12 May 2017 03:43:50 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:52056 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756413AbdELHnr (ORCPT ); Fri, 12 May 2017 03:43:47 -0400 Date: Fri, 12 May 2017 09:43:22 +0200 (CEST) From: Thomas Gleixner To: Michael Ellerman cc: Rob Landley , Linus Torvalds , "Eric W. Biederman" , Al Viro , Oleg Nesterov , Linux Kernel Mailing List Subject: Re: Is there an recommended way to refer to bitkeepr commits? In-Reply-To: <87r2zuc08d.fsf@concordia.ellerman.id.au> Message-ID: References: <87k25ol41u.fsf@xmission.com> <87h90rj2ub.fsf@concordia.ellerman.id.au> <1de8bc32-ebac-141a-080a-ef1c5a149904@landley.net> <87r2zuc08d.fsf@concordia.ellerman.id.au> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 12 May 2017, Michael Ellerman wrote: > 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. That's correct. I did not include the BK revisions when I imported the commits into the history git. I did not see any reason to do so. I still have no idea what the value would have been or why anyone wants to reference them at all. Thanks, tglx