From: Michael J Gruber <git@drmicha.warpmail.net>
To: Junio C Hamano <gitster@pobox.com>, Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org, hvoigt@hvoigt.net, dev+git@drbeat.li
Subject: Re: [PATCH] Documentation/SubmittingPatches: add quotes to advised commit reference
Date: Mon, 29 Aug 2016 13:24:28 +0200 [thread overview]
Message-ID: <389d314d-5f68-b195-3268-4234440ca4ba@drmicha.warpmail.net> (raw)
In-Reply-To: <xmqqk2f3duf2.fsf@gitster.mtv.corp.google.com>
Junio C Hamano venit, vidit, dixit 27.08.2016 00:42:
> Stefan Beller <sbeller@google.com> writes:
>
>> Junio finds it is easier to read text when the commit subject is quoted.
>>
>> Signed-off-by: Stefan Beller <sbeller@google.com>
>> ---
>> Documentation/SubmittingPatches | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
>> index 500230c..a591229 100644
>> --- a/Documentation/SubmittingPatches
>> +++ b/Documentation/SubmittingPatches
>> @@ -123,7 +123,7 @@ 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)
>> +like this: "Commit f86a374 ("pack-bitmap.c: fix a memleak", 2015-03-30)
>> noticed [...]".
>
> Thanks, but it is not sufficient as you would not see the need for
> quoting without the example.
>
> My preference is not a main deciding factor in this case anyway. A
> more important reason why it makes sense to quote (aside from the
> fact that it makes more sense when reading) is because we already
> have a tool support for that.
>
> Perhaps something like this instead?
>
> -- >8 --
> From: Beat Bolli <dev+git@drbeat.li>
> Subject: SubmittingPatches: use gitk's "Copy commit summary" format
> Date: Fri, 26 Aug 2016 18:59:01 +0200
>
> Update the suggestion in 175d38ca ("SubmittingPatches: document how
> to reference previous commits", 2016-07-28) on the format to refer
> to a commit to match what gitk has been giving since last year with
> its "Copy commit summary" command; also mention this as one of the
> ways to obtain a commit reference in this format.
>
> Signed-off-by: Beat Bolli <dev+git@drbeat.li>
> ---
> Documentation/SubmittingPatches | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 500230c..15adb86 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -122,9 +122,14 @@ 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 [...]".
> +branch, use the format "abbreviated sha1 (subject, date)",
> +with the subject enclosed in a pair of double-quotes, like this:
> +
> + Commit f86a374 ("pack-bitmap.c: fix a memleak", 2015-03-30)
> + noticed that ...
> +
> +The "Copy commit summary" command of gitk can be used to obtain this
> +format.
or (an alias for) the command
git show -s --date=format:%F --pretty='tformat:%h ("%s", %ad)'
>
> (3) Generate your patch using Git tools out of your commits.
>
prev parent reply other threads:[~2016-08-29 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 22:27 [PATCH] Documentation/SubmittingPatches: add quotes to advised commit reference Stefan Beller
2016-08-26 22:42 ` Junio C Hamano
2016-08-26 22:45 ` Stefan Beller
2016-08-27 8:04 ` Jakub Narębski
2016-08-29 18:18 ` Junio C Hamano
2016-08-29 11:24 ` Michael J Gruber [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=389d314d-5f68-b195-3268-4234440ca4ba@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=dev+git@drbeat.li \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=sbeller@google.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).