From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "(" <paren@disroot.org>, 58648@debbugs.gnu.org
Subject: [bug#58648] [PATCH v2] doc: contributing: Expand "Sending a Patch Series".
Date: Sat, 22 Oct 2022 14:20:02 +0200 [thread overview]
Message-ID: <f018d64603d25399c8b8aece355c6b6b5b03ef76.camel@gmail.com> (raw)
In-Reply-To: <CNSF27XRN0MP.2WW66NOBJNEN4@guix-framework>
Am Samstag, dem 22.10.2022 um 12:30 +0100 schrieb (:
> On Sat Oct 22, 2022 at 12:21 PM BST, Liliana Marie Prikler wrote:
> > Also, this series makes it look as though we're only considering
> > multi-
> > patch series. Is the simple case of a single patch still covered?
>
> $ git format-patch -1 --cover-letter --base=auto -o outgoing
>
> works fine for a single patch. In my opinion, you should send a
> cover letter for every set of patches, even if the set only contains
> a single patch.
>
> -- (
I kindly disagree. With single patches, you can add notes below the
dashed line and send less bytes over avian carriers.
next prev parent reply other threads:[~2022-10-22 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 21:57 [bug#58648] [PATCH 0/1] doc: contributing: Expand "Sending a Patch Series" ( via Guix-patches via
2022-10-19 22:00 ` [bug#58648] [PATCH 1/1] " ( via Guix-patches via
2022-10-20 8:56 ` zimoun
2022-10-20 8:59 ` ( via Guix-patches via
2022-10-20 14:13 ` [bug#58648] [PATCH v2] " ( via Guix-patches via
2022-10-22 11:21 ` Liliana Marie Prikler
2022-10-22 11:30 ` ( via Guix-patches via
2022-10-22 12:20 ` Liliana Marie Prikler [this message]
2022-10-28 14:41 ` zimoun
2022-10-25 18:42 ` [bug#58648] [PATCH v3] " ( via Guix-patches via
2022-10-25 19:18 ` Liliana Marie Prikler
2022-10-25 19:23 ` ( via Guix-patches via
2022-10-28 14:04 ` zimoun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f018d64603d25399c8b8aece355c6b6b5b03ef76.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=58648@debbugs.gnu.org \
--cc=paren@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).