Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Maxime Ripard <mripard@kernel.org>
Cc: tools@kernel.org
Subject: Re: b4 adds changelog before the cover letter
Date: Tue, 21 May 2024 13:44:04 -0400	[thread overview]
Message-ID: <20240521-silky-natural-tapir-80defb@lemur> (raw)
In-Reply-To: <20240521-curious-obedient-dove-cc79a8@houat>

On Tue, May 21, 2024 at 12:38:57PM GMT, Maxime Ripard wrote:
> I've just noticed that after sending a series, b4 add the changes 
> before
> the rest of the cover letter.
> 
> For example, I've just sent this series:
> https://lore.kernel.org/r/20240521-kms-hdmi-connector-state-v14-0-51950db4fedb@kernel.org
> 
> Prior to sending the series, this was the commit containing the cover letter:
> https://github.com/mripard/linux/commit/062e28a73fd2
> 
> Right after b4 send was done, this is now the commit:
> https://github.com/mripard/linux/commit/0d20a4123b4435c41177e2cc9122f7d335f7399e
> 
> It's not clear to me what is going on, but other series on other
> machines with the same system and b4 versions don't show the same
> behaviour, so it's probably an unlikely bug, or related to the local
> configuration.

This is because normally there would be a --- between the trailers and 
the changelog, e.g.:

  Cc: linux-rockchip@lists.infradead.org
  Cc: linux-sunxi@lists.linux.dev
  Signed-off-by: Maxime Ripard <mripard@kernel.org>
  ---

  Changes in v14:

That "---" is crucial for us to properly find the start of the changelog 
section. This logic can certainly be improved to be less fragile, but 
for the moment putting back the --- is the only way to fix this for you.

-K

  reply	other threads:[~2024-05-21 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 10:38 b4 adds changelog before the cover letter Maxime Ripard
2024-05-21 17:44 ` Konstantin Ryabitsev [this message]
2024-05-22  7:38   ` Maxime Ripard

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=20240521-silky-natural-tapir-80defb@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=mripard@kernel.org \
    --cc=tools@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