[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aW_qrP-m2iVgiPJn@black.igk.intel.com>
Date: Tue, 20 Jan 2026 21:50:52 +0100
From: "Shevchenko, Andriy" <andriy.shevchenko@...el.com>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Mehta, Sohil" <sohil.mehta@...el.com>,
Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>,
Ingo Molnar <mingo@...hat.com>, "Kohler, Jon" <jon@...anix.com>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Thomas Gleixner <tglx@...nel.org>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [PATCH 1/6] x86/cpu: Break Vendor/Family/Model macros into
separate header
On Tue, Jan 20, 2026 at 04:48:55PM +0000, Luck, Tony wrote:
> > > Signed-off-by: Dave Hansen <dave.hansen@...ux.intel.com>
> >
> > Still don't understand why people putting Cc list before the cutter. This noise
> > in the commit message and when retrospectively one reads on the small screen (I
> > do on the phone from time to time) it makes it at bare miniumum inconvenient).
> >
> > > Cc: Thomas Gleixner <tglx@...nel.org>
> > > Cc: Ingo Molnar <mingo@...hat.com>
> > > Cc: Borislav Petkov <bp@...en8.de>
> > > Cc: Dave Hansen <dave.hansen@...ux.intel.com>
> > > Cc: "H. Peter Anvin" <hpa@...or.com>
> > > Cc: Tony Luck <tony.luck@...el.com>
> > > Cc: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
> > > Cc: "Peter Zijlstra (Intel)" <peterz@...radead.org>
> > > Cc: x86@...nel.org
> > > Cc: Jon Kohler <jon@...anix.com>
> > > ---
>
> I put stuff above the "---" because I'm a dinosaur using GIT and often use:
>
> $ git format-patch ....
>
> ...
>
> $ git am 00*
I couldn't imagine why I would need to use this flow for my own changes.
We have rebase, worktree, multiple remotes in one tree, etc. I think
the keyword is 'dinosaur' and now is 21st century :-)
> to rebase, reorder, move bits from one patch to another, or generate a new
> version of the series. When I do so the "git am" drops everything after the "---" cut line.
>
> I poked around, but couldn't find any way to make "git am" keep it :-(
That's the idea, to get them dropped when a maintainer applies the series.
lore.kernel.org will keep the list anyway.
Haven't researched `b4 relay`, maybe that one helps to carry the Cc list on...
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists