From: Jacob Keller <jacob.keller@gmail.com>
Date: Thu, 16 Jul 2015 00:59:46 GMT
Subject: Re: [PATCH] gitk: Add a "Copy commit summary" command
Message-ID: <CA+P7+xrKc_t6_ntc0jFoHJgYrira74+swqy5kFuuFn_gC9Ft2Q@mail.gmail.com>
In-Reply-To: <CAPig+cTf3WDHf++Ck-SXgY4LRm7WRLLk2BvewUQZktfdpHL4BA@mail.gmail.com>

Agreed. I haven't seen "commit" used much in the past, and you can
easily type that out as it is.

On Wed, Jul 15, 2015 at 4:58 PM, Eric Sunshine <sunshine@sunshineco.com> wrote:
> On Wed, Jul 15, 2015 at 6:24 PM, Keller, Jacob E
> <jacob.e.keller@intel.com> wrote:
>> On Tue, 2015-07-14 at 13:34 -0700, Stefan Beller wrote:
>>> On Tue, Jul 14, 2015 at 9:42 AM,  <dev+git@drbeat.li> wrote:
>>> > From: Beat Bolli <dev+git@drbeat.li>
>>> >
>>> > When referencing earlier commits in new commit messages or other
>>> > text,
>>> > one of the established formats is
>>> >
>>> >     commit <abbrev-sha> ("<summary>", <author-date>)
>>>
>>> That sounds like I would use it a lot! Thanks :)
>>>
>>
>> Yep, quite useful. Also, the kernel suggests using it as a tag like so
>>
>> Fixes: <abbrev-sha> ("summary")
>
> Dropping the literal word "commit" would make this use-case more
> convenient, as well as the typical use-case when composing commit
> messages: "Since <abrrev-sha1> ("blah", <date>), foobar.c has
> flabble-nabbered the wonka-doodle..."
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html