From: Jacob Keller <jacob.keller@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: "Keller, Jacob E" <jacob.e.keller@intel.com>,
"sbeller@google.com" <sbeller@google.com>,
"dev+git@drbeat.li" <dev+git@drbeat.li>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"paulus@samba.org" <paulus@samba.org>
Subject: Re: [PATCH] gitk: Add a "Copy commit summary" command
Date: Wed, 15 Jul 2015 17:59:46 -0700 [thread overview]
Message-ID: <CA+P7+xrKc_t6_ntc0jFoHJgYrira74+swqy5kFuuFn_gC9Ft2Q@mail.gmail.com> (raw)
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
prev parent reply other threads:[~2015-07-16 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 16:42 [PATCH] gitk: Add a "Copy commit summary" command dev+git
2015-07-14 20:34 ` Stefan Beller
2015-07-15 22:24 ` Keller, Jacob E
2015-07-15 23:58 ` Eric Sunshine
2015-07-16 0:59 ` Jacob Keller [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=CA+P7+xrKc_t6_ntc0jFoHJgYrira74+swqy5kFuuFn_gC9Ft2Q@mail.gmail.com \
--to=jacob.keller@gmail.com \
--cc=dev+git@drbeat.li \
--cc=git@vger.kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=paulus@samba.org \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.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).