git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Beat Bolli <dev+git@drbeat.li>
Cc: Git List <git@vger.kernel.org>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH v3] gitk: Add a "Copy commit summary" command
Date: Fri, 17 Jul 2015 13:17:33 -0400	[thread overview]
Message-ID: <CAPig+cR=u_ak_=J=gSAWfiNB01R7FBG+bCrx+k1HNAE0xHtwFQ@mail.gmail.com> (raw)
In-Reply-To: <205a18f7f8a7892a1fa63a91a84bfd9b@drbeat.li>

On Fri, Jul 17, 2015 at 4:39 AM, Beat Bolli <dev+git@drbeat.li> wrote:
> When referring to earlier commits in commit messages or other text, one
> of the established formats is
>
>     <abbrev-sha> ("<summary>", <author-date>)
>
> Add a "Copy commit summary" command to the context menu that puts this
> text for the currently selected commit on the clipboard. This makes it
> easy for our users to create well-formatted commit references.
>
> The <abbrev-sha> is produced with the %h format specifier to make it
> unique. Its minimum length can be controlled with the config setting
> core.abbrev.
>
> Signed-off-by: Beat Bolli <dev+git@drbeat.li>
> Reviewed-by: Eric Sunshine <sunshine@sunshineco.com>
> Reviewed-by: Johannes Sixt <j6t@kdbg.org>

You should drop these Reviewed-by: footers, as they imply that the
code was thoroughly digested and the implementation deemed correct.
Hannes at least gave advice about abbreviation length and may deserve
mention via a Helped-by: footer (if you take his advice and feel his
contribution worthy); however, in my case, I merely made a very minor
observation about the output format, not even worth a Helped-by: (and
certainly not a Reviewed-by:).

> Cc: Paul Mackerras <paulus@samba.org>
>
> ---
> Changes since v2:
> - call git log to produce a unique <abbrev-sha>
> - use the short date format
>
> Changes since v1:
> - drop the "commit " literal in front of the <abbrev-sha>
> ---
>  gitk-git/gitk | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
>
> diff --git a/gitk-git/gitk b/gitk-git/gitk
> index 9a2daf3..4915f53 100755
> --- a/gitk-git/gitk
> +++ b/gitk-git/gitk
> @@ -2617,6 +2617,7 @@ proc makewindow {} {
>         {mc "Diff selected -> this" command {diffvssel 1}}
>         {mc "Make patch" command mkpatch}
>         {mc "Create tag" command mktag}
> +       {mc "Copy commit summary" command copysummary}
>         {mc "Write commit to file" command writecommit}
>         {mc "Create new branch" command mkbranch}
>         {mc "Cherry-pick this commit" command cherrypick}
> @@ -9341,6 +9342,17 @@ proc mktaggo {} {
>      mktagcan
>  }
>
> +proc copysummary {} {
> +    global rowmenuid
> +
> +    set format "%h (\"%s\", %ad)"
> +    set summary [exec git show -s --pretty=format:$format --date=short \
> +                 $rowmenuid]
> +
> +    clipboard clear
> +    clipboard append $summary
> +}
> +
>  proc writecommit {} {
>      global rowmenuid wrcomtop commitinfo wrcomcmd NS
>
> --
> 2.4.0

  reply	other threads:[~2015-07-17 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  8:39 [PATCH v3] gitk: Add a "Copy commit summary" command Beat Bolli
2015-07-17 17:17 ` Eric Sunshine [this message]
2015-07-17 17:28   ` Junio C Hamano
2015-07-17 20:59     ` Beat Bolli

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='CAPig+cR=u_ak_=J=gSAWfiNB01R7FBG+bCrx+k1HNAE0xHtwFQ@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=dev+git@drbeat.li \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.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.
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).