workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Alejandro Colomar <alx@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Mark Brown <broonie@kernel.org>, Sasha Levin <sashal@kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Jacob Keller <jacob.e.keller@intel.com>,
	Yeking@red54.com, kuba@kernel.org,
	Jonathan Corbet <corbet@lwn.net>,
	Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
	Dwaipayan Ray <dwaipayanray1@gmail.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, tech-board-discuss@lists.linux.dev,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH] Add short author date to Fixes tag
Date: Wed, 25 Feb 2026 17:35:39 -0500	[thread overview]
Message-ID: <20260225223539.GD16846@macsyma-wired.lan> (raw)
In-Reply-To: <aZ9p2RMrJL1mQ10w@devuan>

On Wed, Feb 25, 2026 at 10:45:48PM +0100, Alejandro Colomar wrote:
> The date gives more information to humans to decide if the commit is
> important to look up.  Sometimes, a subject can be ambiguous to the
> human, even if it's not ambiguous to a machine.  The date can help give
> some context to a human.  For example, one could relate a commit to a
> series that was merged around that date.

I'm really confused under what circumstances the date would ever be
*useful* to me.  In general, what I want to know is "is this fix
applicable to a branch I care about", which basically means I want to
know if a particular branch (a) has the commit id, or (b) has a commit
whose description contains a "commit upstream" line referencing the
commit.

The date is almost never interesting to me.  For upstream commits in
Linus's tree, the hint:

   Cc: stable@kernel.org # 6.8+

Is a bit more interesting to me, but so long as there's a fixes tag
with a commit ID, I can just do a "git tag --contains <commit-id>" to
get the same information.

					- Ted


  reply	other threads:[~2026-02-25 22:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  0:56 Alejandro Colomar
2026-02-25  0:57 ` Alejandro Colomar
2026-02-25 18:00 ` Greg Kroah-Hartman
2026-02-25 18:20   ` Alejandro Colomar
2026-02-25 19:47     ` James Bottomley
2026-02-25 21:23     ` Greg Kroah-Hartman
2026-02-25 21:45       ` Alejandro Colomar
2026-02-25 22:35         ` Theodore Tso [this message]
2026-02-25 23:27         ` Sasha Levin
2026-02-25 23:46         ` Greg Kroah-Hartman
2026-02-26  0:20           ` Alejandro Colomar
2026-02-25 20:08 ` Sasha Levin
2026-02-26  0:08 ` Steven Rostedt
     [not found] <tencent_6CF6E720909156A227D23AE8CFE4F9BA5D05@qq.com>
2025-01-10 12:20 ` Yeking
2025-01-10 12:32   ` Greg Kroah-Hartman
2025-01-10 13:03   ` Steven Rostedt
2025-01-11  0:21     ` Jacob Keller
2025-01-11  5:48       ` Greg Kroah-Hartman
2025-01-11 17:09       ` Steven Rostedt
2025-01-12 10:54         ` Geert Uytterhoeven
2025-01-13 14:51           ` Steven Rostedt
2025-01-13 15:08             ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260225223539.GD16846@macsyma-wired.lan \
    --to=tytso@mit.edu \
    --cc=Yeking@red54.com \
    --cc=akpm@linux-foundation.org \
    --cc=alx@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=apw@canonical.com \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dwaipayanray1@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jacob.e.keller@intel.com \
    --cc=joe@perches.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=tech-board-discuss@lists.linux.dev \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox