Re: Proposal: Enhancing Commit Tagging for Stable Kernel Branches

[Greg KH <gregkh@linuxfoundation.org>]

On Mon, Jul 15, 2024 at 02:39:59PM -0500, Dan Carpenter wrote:
> On Mon, Jul 15, 2024 at 03:24:42PM -0400, James Bottomley wrote:
> > On Mon, 2024-07-15 at 14:06 -0500, Dan Carpenter wrote:
> > [...]
> > > The one question I have is for patches which pre-date git.  I was
> > > told to leave the Fixes tag off in that case, but I think that's out
> > > of date. It's more useful to say "Fixes: 1da177e4c3f4 ("Linux-2.6.12-
> > > rc2")".
> > 
> > Actually, we have a history tree (based on Bitkeeper) that goes back
> > before that:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/
> > 
> > So I'd tag these as
> > 
> > Fixes: 3bc0a5f5c1 (history "ext3: reservation info cleanup")
> 
> I don't think most people have the ancient history so would just confuse
> people and break scripts.

Yes, as an example, it breaks mine which I use to find out how far back
a commit should be backported to.  For the above, it gives:
	Could not get sha1 for 3bc0a5f5c1. Skipping.
as an output :(

thanks,

greg k-h