[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250111120935.769ab9a3@gandalf.local.home>
Date: Sat, 11 Jan 2025 12:09:35 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Jacob Keller <jacob.e.keller@...el.com>
Cc: <Yeking@...54.com>, <kuba@...nel.org>, Jonathan Corbet <corbet@....net>,
Theodore Ts'o <tytso@....edu>, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>, "Andy Whitcroft" <apw@...onical.com>, Joe
Perches <joe@...ches.com>, Dwaipayan Ray <dwaipayanray1@...il.com>, Lukas
Bulwahn <lukas.bulwahn@...il.com>, "Andrew Morton"
<akpm@...ux-foundation.org>, <workflows@...r.kernel.org>,
<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<tech-board-discuss@...ts.linux.dev>
Subject: Re: [PATCH] Add short author date to Fixes tag
On Fri, 10 Jan 2025 16:21:35 -0800
Jacob Keller <jacob.e.keller@...el.com> wrote:
> I personally find the date helpful as it can help place a commit without
> needing to take the extra time to do a lookup.
I've never found dates to be meaningful. I'm always more concerned about
when a commit was added to mainline. Thus the version where the commit was
added is very important for me. This is why I keep a bare clone of Linus's
tree and commonly do:
$ git describe --contains fd3040b9394c
v5.19-rc1~159^2~154^2
$ git describe --contains a76053707dbf
v5.15-rc1~157^2~376^2~4
I can easily see that a76053707dbf was added in 5.15 and fd3040b9394c was
added in 5.19. The amount of work needed to add dates to Fixes tags would
greatly exceed the amount of added work someone would need to do to do the
above operations if they wanted to know the order of commits.
-- Steve
Powered by blists - more mailing lists