git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Michael Rappazzo <rappazzo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitk: Add mouse right-click options
Date: Sun, 17 May 2015 10:56:57 +1000	[thread overview]
Message-ID: <20150517005657.GB21039@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <1431052160-82758-1-git-send-email-rappazzo@gmail.com>

On Thu, May 07, 2015 at 10:29:19PM -0400, Michael Rappazzo wrote:
> I work in a large and deep codebase, and found it useful to have these additional features in gitk.  
> 
> First, in the commit list, a right click on a branch name will add an option ('Copy branch name') to put that name on the system clipboard.
> 
> Second, in the file list of a commit, a right click on a file will add an option ('Copy path') to put the file path on the system clipboard.

Thanks, applied.

Paul.

      parent reply	other threads:[~2015-05-17  4:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  2:29 [PATCH] gitk: Add mouse right-click options Michael Rappazzo
2015-05-08  2:29 ` Michael Rappazzo
2015-05-17  0:56 ` Paul Mackerras [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150517005657.GB21039@iris.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=git@vger.kernel.org \
    --cc=rappazzo@gmail.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).