git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Fahlke <flyingmana@cotya.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com
Subject: Re: [PATCH] show signature of commit in gitk
Date: Sun, 13 Dec 2015 15:15:30 +0100	[thread overview]
Message-ID: <566D7D82.90107@cotya.com> (raw)
In-Reply-To: <565F443D.7050205@cotya.com>

It seems my Patch got no attention yet, is there anything wrong? 
Do I need to ping someone in particular?

On 12/02/2015 08:19 PM, Daniel Fahlke wrote:
> but still depending on the added --show-signature as argument
> 
> longer explanation:
> git supports for some time now signed commits, and also show the
> signature and its trust level inside the `git log` command.
> Now, it can also get shown in gitk.
> 
> Signed-off-by: Flyingmana <flyingmana@googlemail.com>
> ---
>  gitk-git/gitk | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/gitk-git/gitk b/gitk-git/gitk
> index fcc606e..54c167f 100755
> --- a/gitk-git/gitk
> +++ b/gitk-git/gitk
> @@ -1674,6 +1674,7 @@ proc parsecommit {id contents listed} {
>      set audate {}
>      set comname {}
>      set comdate {}
> +    set comgpg {}
>      set hdrend [string first "\n\n" $contents]
>      if {$hdrend < 0} {
>  	# should never happen...
> @@ -1690,6 +1691,9 @@ proc parsecommit {id contents listed} {
>  	} elseif {$tag == "committer"} {
>  	    set comdate [lrange $line end-1 end]
>  	    set comname [join [lrange $line 1 end-2] " "]
> +	} elseif {$tag == "gpg:"} {
> +	    append comgpg [join [lrange $line 1 end] " "]
> +	    append comgpg "\n"
>  	}
>      }
>      set headline {}
> @@ -1726,7 +1730,7 @@ proc parsecommit {id contents listed} {
>  	set comment [string range $comment 0 $i-1]
>      }
>      set commitinfo($id) [list $headline $auname $audate \
> -			     $comname $comdate $comment $hasnote $diff]
> +			     $comname $comdate $comment $hasnote $diff $comgpg]
>  }
>   proc getcommit {id} {
> @@ -7325,6 +7329,7 @@ proc selectline {l isnew {desired_loc {}}
> {switch_to_patch 0}} {
>      $ctext insert end "[mc "Author"]: [lindex $info 1]  $date\n"
>      set date [formatdate [lindex $info 4]]
>      $ctext insert end "[mc "Committer"]: [lindex $info 3]  $date\n"
> +    $ctext insert end [lindex $info 8]
>      if {[info exists idtags($id)]} {
>  	$ctext insert end [mc "Tags:"]
>  	foreach tag $idtags($id) {
> 

  reply	other threads:[~2015-12-13 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 19:19 [PATCH] show signature of commit in gitk Daniel Fahlke
2015-12-13 14:15 ` Daniel Fahlke [this message]
2015-12-13 18:10   ` Mike Rappazzo

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=566D7D82.90107@cotya.com \
    --to=flyingmana@cotya.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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 NNTP newsgroup(s).