aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLinus Arver <linusa@google.com>2024-04-18 21:52:00 +0000
committerJunio C Hamano <gitster@pobox.com>2024-04-18 14:55:10 -0700
commit84b91fc465a869cfb30084dca1831e432461e18a (patch)
tree23882add2766d6955384e2b747e4a23c558cf2f8
parent824503ce88963b9d7f111215fdce073a504e76e7 (diff)
downloadgit-84b91fc465a869cfb30084dca1831e432461e18a.tar.gz
SubmittingPatches: mention GitGitGadget
Signed-off-by: Linus Arver <linusa@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/SubmittingPatches4
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index d4173d4fe8..26055a1fe2 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -408,6 +408,10 @@ are optimized for the workflow of sending patches, avoiding many ways
your existing e-mail client (often optimized for "multipart/*" MIME
type e-mails) might render your patches unusable.
+NOTE: Here we outline the procedure using `format-patch` and
+`send-email`, but you can instead use GitGitGadget to send in your
+patches (see link:MyFirstContribution.html[MyFirstContribution]).
+
People on the Git mailing list need to be able to read and
comment on the changes you are submitting. It is important for
a developer to be able to "quote" your changes, using standard