[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251125-heavenly-agile-seahorse-161893@lemur>
Date: Tue, 25 Nov 2025 11:02:38 -0500
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Shrikanth Hegde <sshegde@...ux.ibm.com>,
Greg KH <gregkh@...uxfoundation.org>, linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
mingo@...hat.com, peterz@...radead.org, juri.lelli@...hat.com,
vincent.guittot@...aro.org, tglx@...utronix.de, yury.norov@...il.com, maddy@...ux.ibm.com,
srikar@...ux.ibm.com, pbonzini@...hat.com, seanjc@...gle.com, kprateek.nayak@....com,
vschneid@...hat.com, iii@...ux.ibm.com, huschle@...ux.ibm.com,
dietmar.eggemann@....com, christophe.leroy@...roup.eu
Subject: Re: [PATCH 16/17] sysfs: Provide write method for paravirt
On Tue, Nov 25, 2025 at 10:52:18AM -0500, Steven Rostedt wrote:
> You may also want remove the [ ] and use '--' instead:
>
> [PATCH 16/17] -- DO NOT APPLY!!! -- sysfs: Provide write method for paravirt
>
> Because if someone were to do a b4 pull it would strip out the text within
> the brackets. Using -- DO NOT APPLY!!! -- instead, would keep it in the
> commit message. And then seeing that in the shortlog would be a really big
> red flag ;-)
Small correction -- it's git itself that strips all content inside [], not b4
specifically.
-K
Powered by blists - more mailing lists