git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/2] SubmittingPatches: hint at gitk's "Copy commit summary" command

From
Beat Bolli <dev+git@drbeat.li>
Date
Aug 26, 2016, 16:59 UTC
Message-ID
<1472230741-5161-2-git-send-email-dev+git@drbeat.li>
In-Reply-To
<1472230741-5161-1-git-send-email-dev+git@drbeat.li>

Amend the section on referencing previous commits with a hint to the gitk command that was added exactly for this purpose.

Signed-off-by: Beat Bolli <dev+git@drbeat.li>
---
 Documentation/SubmittingPatches | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 500230c..94a1661 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -124,7 +124,8 @@ 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 [...]".
+noticed [...]". The "Copy commit summary" command of gitk generates this
+format.
 
 
 (3) Generate your patch using Git tools out of your commits.
-- 
2.7.2
Previous: Beat BolliNext: Junio C Hamano
Message 2 of 12 in “gitk: align the commit summary format to the documentation”
  1. 1/2 gitk: align the commit summary format to the documentationBeat Bolli, Aug 26, 2016
  2. 2/2 SubmittingPatches: hint at gitk's "Copy commit summary" commandBeat Bolli, Aug 26, 2016
  3. Junio C HamanoAug 26, 2016
  4. Jacob KellerAug 27, 2016
  5. Junio C HamanoAug 26, 2016
  6. Stefan BellerAug 26, 2016
  7. Beat BolliAug 26, 2016
  8. Junio C HamanoAug 26, 2016
  9. Stefan BellerAug 26, 2016
  10. Johannes SixtAug 27, 2016
  11. Junio C HamanoAug 29, 2016
  12. Jeff KingAug 29, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.