From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
73055@debbugs.gnu.org,
"Florian Pelz" <pelzflorian@pelzflorian.de>
Subject: [bug#73055] [PATCH] doc: Explain `git format-patch` revision format
Date: Sun, 08 Sep 2024 22:31:51 +0900 [thread overview]
Message-ID: <87tteqe0fs.fsf@gmail.com> (raw)
In-Reply-To: <7098b72d119941801db2c9f38a8a4f2dde03b540.1725562109.git.ekaitz@elenq.tech> (Ekaitz Zarraga's message of "Thu, 5 Sep 2024 20:48:29 +0200")
Hi Ekaitz,
Ekaitz Zarraga <ekaitz@elenq.tech> writes:
> * doc/contributing.texi(Sending a Patch Series): Add a note about
> `git format-patch` revision format and link to git documentation.
>
> Change-Id: Ie08f85dc19e3804165fb184664b74e85a804d7c4
> ---
> doc/contributing.texi | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/doc/contributing.texi b/doc/contributing.texi
> index 73f7addbef..d5d63ebdbd 100644
> --- a/doc/contributing.texi
> +++ b/doc/contributing.texi
> @@ -2187,6 +2187,18 @@ Sending a Patch Series
> --cover-letter --base=auto
> @end example
>
> +@quotation Note
> +@code{git format-patch} accepts a wide range of
> +@uref{https://git-scm.com/docs/gitrevisions, revision range} specifiers.
> +For example, if you are working in a branch, you could select all commits
> +in your branch starting at @code{master}.
> +
> +@example
> +$ git format-patch master..@var{MY_BRANCH} -o outgoing \
> + --cover-letter --base=auto
The --base=auto can be dropped since it's part of our default git
config, which is automatically installed for all of our contributors
(c.f.: etc/git/gitconfig) when they build the Guix source.
Otherwise, LGTM, if others think it has enough value to be added.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-09-08 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 18:48 [bug#73055] [PATCH] doc: Explain `git format-patch` revision format Ekaitz Zarraga
2024-09-08 13:31 ` Maxim Cournoyer [this message]
2024-09-08 20:16 ` Ekaitz Zarraga
2024-09-09 2:53 ` Maxim Cournoyer
2024-09-09 14:12 ` [bug#73055] [PATCH] doc: contributing: Remove --base=auto Ekaitz Zarraga
2024-09-10 2:54 ` Maxim Cournoyer
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=87tteqe0fs.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=73055@debbugs.gnu.org \
--cc=ekaitz@elenq.tech \
--cc=ludo@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).