Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Tools <tools@linux.kernel.org>
Subject: Re: asdf
Date: Fri, 21 Apr 2023 14:52:33 -0400	[thread overview]
Message-ID: <20230421-carpentry-aviator-eb2a5a@meerkat> (raw)
In-Reply-To: <20230331-ranged-decrease-6027cce938ff@brauner>

On Fri, Mar 31, 2023 at 12:04:14PM +0200, Christian Brauner wrote:
> Can't be said enough: thanks for b4!

Glad to see so many people start to use it.

> I have two inquiries about b4 send:
> 
> (1) Currently the message id that is generated for each patch sent by b4
>     has the format:
> 
>     [date] - [branch name] - [version] - [patch number] - [random] @ kernel.org
> 
>     where [date] is fixed and is taken from the change-id of the series
>     as you mentioned in a fediverse thread.
> 
>     It would be nice if we could - potentially opt-in via a config opt -
>     set [date] to the date when the patch series was sent.

Sounds reasonable.
bugbot on

> (2) I couldn't find an option to tell b4 send to set In-Reply-To: to one
>     or more messages. That comes in handy when e.g., generating a patch
>     in reply to syzbot report.
> 
> Maybe that's something worth adding.

I worry that this can create really weird thread interactions. E.g. if you
have a bot report and it results in two different series being proposed:

original bot report
 \ 
  -- [PATCH] fixes one issue from the report
  \
 | -- [PATCH v2] fixes one issue from the report
 |
  -- [PATCH] fixes a different issue from the report
  \
   -- [PATCH v2] fixes a different issue from the report

This will confuse absolutely everyone, not just b4. :)
It's best to just use Link:, I think.

-K

  reply	other threads:[~2023-04-21 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 10:04 asdf Christian Brauner
2023-04-21 18:52 ` Konstantin Ryabitsev [this message]
2023-04-21 18:58 ` asdf Kernel.org Bugbot
2023-06-21 20:08 ` b4: individual patch series should have the latest timestamp in the message-id Kernel.org Bugbot

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=20230421-carpentry-aviator-eb2a5a@meerkat \
    --to=konstantin@linuxfoundation.org \
    --cc=brauner@kernel.org \
    --cc=tools@linux.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