All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org,
	"Jonathan Cameron" <jonathan.cameron@huawei.com>,
	"Fan Ni" <fan.ni@samsung.com>,
	"John Levon" <john.levon@nutanix.com>,
	"Thanos Makatos" <thanos.makatos@nutanix.com>,
	"Cédric Le Goater" <clg@redhat.com>,
	"Alex Williamson" <alex@shazbot.org>
Subject: Re: [PATCH 5/9] scripts/clean-includes: Give the args in git commit messages
Date: Fri, 07 Nov 2025 14:44:31 +0100	[thread overview]
Message-ID: <87jz027y9s.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFEAcA96NhaKQGWeMC0Gx9pM36cZfCD4g=xVW58_mWgKg1Qc8Q@mail.gmail.com> (Peter Maydell's message of "Fri, 7 Nov 2025 13:14:12 +0000")

Peter Maydell <peter.maydell@linaro.org> writes:

> On Fri, 7 Nov 2025 at 12:05, Markus Armbruster <armbru@redhat.com> wrote:
>>
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>
>> > If clean-includes is creating a git commit for its changes,
>> > currently it says only "created with scripts/clean-includes".
>> > Add the command line arguments the user passed us, as useful
>> > extra information.
>> >
>> > Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> > ---
>> >  scripts/clean-includes | 6 +++++-
>> >  1 file changed, 5 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/scripts/clean-includes b/scripts/clean-includes
>> > index a45421d2ff7..694e12f062c 100755
>> > --- a/scripts/clean-includes
>> > +++ b/scripts/clean-includes
>> > @@ -42,6 +42,9 @@
>> >  GIT=no
>> >  DUPHEAD=no
>> >
>> > +# Save the original arguments in case we want to put them in
>> > +# a git commit message
>> > +ORIGARGS="$*"
>> >
>> >  while true
>> >  do
>> > @@ -198,7 +201,8 @@ if [ "$GIT" = "yes" ]; then
>> >      git commit --signoff -F - <<EOF
>> >  $GITSUBJ: Clean up includes
>> >
>> > -This commit was created with scripts/clean-includes.
>> > +This commit was created with scripts/clean-includes:
>> > + ./scripts/clean-includes $ORIGARGS
>>
>> Consider
>>
>>     $ ./scripts/clean-includes --git 'a b c' a b c
>
> Yes. Do you have a way to deal with that that isn't
> more complex than justified by what we're doing here?
>
> thanks
> -- PMM

This doesn't feel too onerous:

    args=
    for i
    do args+=" '""$i""'"
    done

However, += is bash.



  reply	other threads:[~2025-11-07 13:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 16:09 [PATCH 0/9] clean-includes: improve exclude list, run on cxl, vfio, tests Peter Maydell
2025-11-04 16:09 ` [PATCH 1/9] scripts/clean-includes: Allow directories on command line Peter Maydell
2025-11-17  9:16   ` Richard Henderson
2025-11-04 16:09 ` [PATCH 2/9] scripts/clean-includes: Remove outdated comment Peter Maydell
2025-11-17  9:17   ` Richard Henderson
2025-11-04 16:09 ` [PATCH 3/9] scripts/clean-includes: Make ignore-regexes one per line Peter Maydell
2025-11-17  9:19   ` Richard Henderson
2025-11-04 16:09 ` [PATCH 4/9] scripts/clean-includes: Do all our exclusions with REGEXFILE Peter Maydell
2025-11-17  9:21   ` Richard Henderson
2025-11-04 16:09 ` [PATCH 5/9] scripts/clean-includes: Give the args in git commit messages Peter Maydell
2025-11-07 12:05   ` Markus Armbruster
2025-11-07 13:14     ` Peter Maydell
2025-11-07 13:44       ` Markus Armbruster [this message]
2025-11-07 15:42         ` Markus Armbruster
2025-11-04 16:09 ` [PATCH 6/9] scripts/clean-includes: Update exclude list Peter Maydell
2025-11-17  9:33   ` Richard Henderson
2025-11-04 16:09 ` [PATCH 7/9] cxl: Clean up includes Peter Maydell
2025-11-04 16:51   ` Philippe Mathieu-Daudé
2025-11-04 16:54   ` Jonathan Cameron via
2025-11-17  9:34   ` Richard Henderson
2025-11-04 16:09 ` [PATCH 8/9] vfio: " Peter Maydell
2025-11-04 16:40   ` Cédric Le Goater
2025-11-04 16:51   ` Philippe Mathieu-Daudé
2025-11-04 16:09 ` [PATCH 9/9] tests: " Peter Maydell
2025-11-04 16:48   ` Cédric Le Goater
2025-11-14 13:19 ` [PATCH 0/9] clean-includes: improve exclude list, run on cxl, vfio, tests Peter Maydell

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=87jz027y9s.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alex@shazbot.org \
    --cc=clg@redhat.com \
    --cc=fan.ni@samsung.com \
    --cc=john.levon@nutanix.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thanos.makatos@nutanix.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.