All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Tools <tools@linux.kernel.org>
Subject: asdf
Date: Fri, 31 Mar 2023 12:04:14 +0200	[thread overview]
Message-ID: <20230331-ranged-decrease-6027cce938ff@brauner> (raw)

Hey Konstantin,

Can't be said enough: thanks for b4!

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.

(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.

Thanks!
Christian

             reply	other threads:[~2023-03-31 10:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 10:04 Christian Brauner [this message]
2023-04-21 18:52 ` asdf Konstantin Ryabitsev
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
  -- strict thread matches above, loose matches on Subject: below --
2024-04-15  0:39 asdf 임준수(Junesoo Im) 수석 두산로보틱스
2011-12-06  8:08 asdf Dan Carpenter
2011-12-06  8:48 ` asdf Kyungmin Park
2011-04-28 12:20 asdf Alexander Simon
2007-02-02  7:22 asdf Tejun Heo
2007-02-02 16:59 ` asdf Ric Wheeler
2007-02-03  4:07   ` asdf Tejun Heo
2006-07-06 10:15 asdf Horms
2004-03-02 21:48 asdf Jonathan
2004-03-02 19:15 asdf Jonathan
2001-10-11 10:53 asdf thunder7

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=20230331-ranged-decrease-6027cce938ff@brauner \
    --to=brauner@kernel.org \
    --cc=konstantin@linuxfoundation.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 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.