Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Johannes Zink <j.zink@pengutronix.de>
To: Mattijs Korpershoek <mkorpershoek@baylibre.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org, kernel@pengutronix.de
Subject: Re: b4: Feature-Request: use salted hash for change-id instead of descriptive-name when using b4 prep
Date: Mon, 5 Jun 2023 09:32:28 +0200	[thread overview]
Message-ID: <19b5d7af-44fb-37ba-6d20-98e53c9154b1@pengutronix.de> (raw)
In-Reply-To: <87edmqjrom.fsf@baylibre.com>

Hi Mattijs,

On 6/5/23 09:26, Mattijs Korpershoek wrote:
>>
[snip]
>>>
>>
>> is that equivalent to do b4 prep --edit-cover?
> 
> No, it is not. b4 prep --edit-cover does not show the
> "--- b4-submit-tracking ---" section that Konstantin recommended you to
> edit.
> 
> You can only edit that with "git commit --amend --allow-empty"
> 

thank you for your explaination and your fast response!

Johannes

> 
>>

-- 
Pengutronix e.K.                | Johannes Zink                  |
Steuerwalder Str. 21            | https://www.pengutronix.de/    |
31137 Hildesheim, Germany       | Phone: +49-5121-206917-0       |
Amtsgericht Hildesheim, HRA 2686| Fax:   +49-5121-206917-5555    |


      reply	other threads:[~2023-06-05  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02  8:00 b4: Feature-Request: use salted hash for change-id instead of descriptive-name when using b4 prep Johannes Zink
2023-06-02 16:50 ` Konstantin Ryabitsev
2023-06-05  6:10   ` Johannes Zink
2023-06-05  7:26     ` Mattijs Korpershoek
2023-06-05  7:32       ` Johannes Zink [this message]

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=19b5d7af-44fb-37ba-6d20-98e53c9154b1@pengutronix.de \
    --to=j.zink@pengutronix.de \
    --cc=kernel@pengutronix.de \
    --cc=konstantin@linuxfoundation.org \
    --cc=mkorpershoek@baylibre.com \
    --cc=tools@linux.kernel.org \
    --cc=users@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).