Skip to content

Commit 175d38c

Browse files
hvoigtgitster
authored andcommitted
SubmittingPatches: document how to reference previous commits
To reference previous commits people used to put just the abbreviated SHA-1 into commit messages. This is what has evolved as a more stable format for referencing commits. So lets document it for everyone to look-up when needed. Signed-off-by: Heiko Voigt <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 0b65a8d commit 175d38c

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

Documentation/SubmittingPatches

+5
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,11 @@ its behaviour. Try to make sure your explanation can be understood
121121
without external resources. Instead of giving a URL to a mailing list
122122
archive, summarize the relevant points of the discussion.
123123

124+
If you want to reference a previous commit in the history of a stable
125+
branch use the format "abbreviated sha1 (subject, date)". So for example
126+
like this: "Commit f86a374 (pack-bitmap.c: fix a memleak, 2015-03-30)
127+
noticed [...]".
128+
124129

125130
(3) Generate your patch using Git tools out of your commits.
126131

0 commit comments

Comments
 (0)