[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#73055] [PATCH] doc: Explain `git format-patch` revision format
From: |
Ekaitz Zarraga |
Subject: |
[bug#73055] [PATCH] doc: Explain `git format-patch` revision format |
Date: |
Thu, 5 Sep 2024 20:48:29 +0200 |
* 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
+@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.
base-commit: 7d2ced8d6d9c38327592d312376d59a8c37fc160
--
2.45.2
- [bug#73055] [PATCH] doc: Explain `git format-patch` revision format,
Ekaitz Zarraga <=