From: Beat Bolli <dev+git@drbeat.li>
To: git@vger.kernel.org
Cc: Beat Bolli <dev+git@drbeat.li>
Subject: [PATCH 2/2] SubmittingPatches: hint at gitk's "Copy commit summary" command
Date: Fri, 26 Aug 2016 18:59:01 +0200 [thread overview]
Message-ID: <1472230741-5161-2-git-send-email-dev+git@drbeat.li> (raw)
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
next prev parent reply other threads:[~2016-08-26 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 16:59 [PATCH 1/2] gitk: align the commit summary format to the documentation Beat Bolli
2016-08-26 16:59 ` Beat Bolli [this message]
2016-08-26 18:27 ` [PATCH 2/2] SubmittingPatches: hint at gitk's "Copy commit summary" command Junio C Hamano
2016-08-27 3:58 ` Jacob Keller
2016-08-26 18:24 ` [PATCH 1/2] gitk: align the commit summary format to the documentation Junio C Hamano
2016-08-26 19:16 ` Stefan Beller
2016-08-26 20:27 ` Beat Bolli
2016-08-26 21:27 ` Junio C Hamano
2016-08-26 22:29 ` Stefan Beller
2016-08-27 7:21 ` Johannes Sixt
2016-08-29 18:17 ` Junio C Hamano
2016-08-29 18:30 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1472230741-5161-2-git-send-email-dev+git@drbeat.li \
--to=dev+git@drbeat.li \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.