Re: Proposal: Enhancing Commit Tagging for Stable Kernel Branches

[James Bottomley <James.Bottomley@HansenPartnership.com>]

On Mon, 2024-07-15 at 15:28 -0400, Steven Rostedt wrote:
> On Mon, 15 Jul 2024 15:24:42 -0400
> James Bottomley <James.Bottomley@HansenPartnership.com> 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 that is necessary. If something is found to be broken
> from before 2005, I don't believe it's worth the effort to search
> another tree for the actual change that introduced the problem. When
> you go that far, it becomes only an academic exercise.

Some people are naturally curious, so it makes sense to have a format
for them even if we don't require everyone to do it.

James