[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH] docs/devel: remove incorrect claim about git send-email

From: Linus Heckemann
Subject: [PATCH] docs/devel: remove incorrect claim about git send-email
Date: Tue, 13 Sep 2022 18:52:14 +0200

While it's unclear to me what git send-email actually does with the
-v2 parameter (it is not documented, but also not rejected), it does
not add a v2 tag to the email's subject, which is what led to the
mishap in [1].

[1]: https://lists.nongnu.org/archive/html/qemu-devel/2022-09/msg00679.html
 docs/devel/submitting-a-patch.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/devel/submitting-a-patch.rst 
index fec33ce148..be2c428b93 100644
--- a/docs/devel/submitting-a-patch.rst
+++ b/docs/devel/submitting-a-patch.rst
@@ -456,8 +456,7 @@ patch need not say "v1", just [PATCH] is sufficient.) For 
patch series,
 the version applies to the whole series -- even if you only change one
 patch, you resend the entire series and mark it as "v2". Don't try to
 track versions of different patches in the series separately.  `git
-format-patch <http://git-scm.com/docs/git-format-patch>`__ and `git
-send-email <http://git-scm.com/docs/git-send-email>`__ both understand
+format-patch <http://git-scm.com/docs/git-format-patch>`__ understands
 the ``-v2`` option to make this easier. Send each new revision as a new
 top-level thread, rather than burying it in-reply-to an earlier
 revision, as many reviewers are not looking inside deep threads for new

reply via email to

[Prev in Thread] Current Thread [Next in Thread]