From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4: introducing b4 shazam (like b4 am -o- | git am)
Date: Thu, 30 Sep 2021 10:45:48 -0400 [thread overview]
Message-ID: <20210930144548.z6gxm2g3jlwfu4zq@nitro.local> (raw)
In-Reply-To: <20210929233053.GE3544071@ziepe.ca>
On Wed, Sep 29, 2021 at 08:30:53PM -0300, Jason Gunthorpe wrote:
> I would suggest a template:
>
> Merge patch series "<cover letter subject>"
>
> David Hildenbrand <david@redhat.com> says:
> ====================
> <over letter body>
> ====================
>
> * mailing-list:
> [..]
>
> Link: http..
> Signed-off-by: ..
>
> As a possible starting point?
Okay, the latest master allows for some minor templating and will use the
proposed netdevy format as the default. Since Signed-off-by can be added by
the git-merge command itself, I'm not adding it into the template unless
I can think of a good reason to do so.
I'm also skipping the mailing-list suggestion, as patches are routinely sent
to any number of lists, so that's bound to be a crowded section.
-K
next prev parent reply other threads:[~2021-09-30 14:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 20:25 b4: introducing b4 shazam (like b4 am -o- | git am) Konstantin Ryabitsev
2021-09-22 17:38 ` Jason Gunthorpe
2021-09-22 18:21 ` Konstantin Ryabitsev
2021-09-28 17:46 ` Jason Gunthorpe
2021-09-29 21:18 ` Konstantin Ryabitsev
2021-09-29 23:30 ` Jason Gunthorpe
2021-09-30 14:45 ` Konstantin Ryabitsev [this message]
2021-10-01 16:20 ` Mark Brown
2021-09-23 8:51 ` Geert Uytterhoeven
2021-09-24 21:08 ` Konstantin Ryabitsev
2021-09-28 18:22 ` Geert Uytterhoeven
2021-09-29 13:39 ` Rob Herring
2021-09-29 17:54 ` Geert Uytterhoeven
2021-09-29 18:07 ` Jason Gunthorpe
2021-09-29 14:27 ` Konstantin Ryabitsev
2021-10-19 14:49 ` Rob Herring
2021-10-19 16:30 ` Konstantin Ryabitsev
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=20210930144548.z6gxm2g3jlwfu4zq@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--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 NNTP newsgroup(s).