aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEkaitz Zarraga <ekaitz@elenq.tech>2024-09-05 20:48:29 +0200
committerEkaitz Zarraga <ekaitz@elenq.tech>2024-12-03 22:42:54 +0100
commit7b46b8db9afac3825518dca10b5ff0eab04f5f08 (patch)
treeee58f36a44d5edd7138cfee3458eb8be6ca713d4 /doc
parent595fb0ade7086aa7ebaf7b9bdd9bb8ec83ecd86f (diff)
downloadguix-7b46b8db9afac3825518dca10b5ff0eab04f5f08.tar.gz
guix-7b46b8db9afac3825518dca10b5ff0eab04f5f08.zip
doc: Explain `git format-patch` revision format
* doc/contributing.texi(Sending a Patch Series): Add a note about `git format-patch` revision format and link to git documentation. Change-Id: Ie08f85dc19e3804165fb184664b74e85a804d7c4
Diffstat (limited to 'doc')
-rw-r--r--doc/contributing.texi12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 6be879fa66..816a226ced 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -2194,6 +2194,18 @@ $ git format-patch -@var{NUMBER_COMMITS} -o outgoing \
--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
+@end example
+@end quotation
+
We can now send @emph{just} the cover letter to the
@email{guix-patches@@gnu.org} address, which will create an issue
that we can send the rest of the patches to.