summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-08-25 13:55:05 -0700
committerJunio C Hamano <gitster@pobox.com>2016-08-25 13:55:06 -0700
commita1f0b4e286a81898b70628c5df85bebec653deab (patch)
tree91e6cb19e7506b1fd7c61e65dfb8e4b86f96cc57
parent41a616dadaf2a7445ea7c3f5d77a20337af4de90 (diff)
parent175d38ca231d0dd9cca3bbebae40f797346a850d (diff)
downloadgit-a1f0b4e286a81898b70628c5df85bebec653deab.tar.gz
Merge branch 'hv/doc-commit-reference-style'
A small doc update. * hv/doc-commit-reference-style: SubmittingPatches: document how to reference previous commits
-rw-r--r--Documentation/SubmittingPatches5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index e8ad978824..500230c054 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -121,6 +121,11 @@ its behaviour. Try to make sure your explanation can be understood
without external resources. Instead of giving a URL to a mailing list
archive, summarize the relevant points of the discussion.
+If you want to reference a previous commit in the history of a stable
+branch use the format "abbreviated sha1 (subject, date)". So for example
+like this: "Commit f86a374 (pack-bitmap.c: fix a memleak, 2015-03-30)
+noticed [...]".
+
(3) Generate your patch using Git tools out of your commits.