Re: [PATCH RESEND v4 0/3] livepatch: Move modules to selftests and add a new test

From: Marcos Paulo de Souza <mpdesouza@suse.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: [PATCH RESEND v4 0/3] livepatch: Move modules to selftests and add a new test
Date: Fri, 22 Dec 2023 15:52:29 -0300	[thread overview]
Message-ID: <f5c38763b4d42cfafdaac24d83ec18b81dfc073a.camel@suse.com> (raw)
In-Reply-To: <20231222-horned-caiman-of-freedom-3fec0a@lemur>

On Fri, 2023-12-22 at 13:40 -0500, Konstantin Ryabitsev wrote:
> On Thu, Dec 21, 2023 at 09:17:04AM -0300, Marcos Paulo de Souza
> wrote:
> > To clarify: this is not a resend, this is the v4 that people were
> > waiting for. I made a mistake with b4 tool, that first I sent the
> > email
> > just to myself, for testing, and it bumped the version to v5, but I
> > asked it to "resend" the v4, but it ended up adding the "RESEND" to
> > the
> > series.
> 
> Thank you for sharing that. The expected workflow here would be to
> use
> --reflect first if you wanted to send something to yourself. Can you
> think of
> a way that this experience can be less unexpected?

So my usecase was that I first sent the patches locally to my
colleagues, so I used
	b4 send --no-trailer-to-cc --to
colleague1@suse.com,colleague2@suse.com

Well, maybe adding a confirmation for the user that the version will be
bumped. A new flag could also be created b4 send --keep-version to send
without bumping, thus avoiding the prompt?

Is this too convoluted?

Thanks!
  Marcos

> 
> (Dropping everyone else from cc's and adding the tools list)
> 
> -K