From: "Shawn O. Pearce" <spearce@spearce.org>
To: Eric Wong <normalperson@yhbt.net>
Cc: Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] gitk: bind <F5> key to Update (reread commits)
Date: Fri, 23 Feb 2007 15:41:13 -0500 [thread overview]
Message-ID: <20070223204113.GA27261@spearce.org> (raw)
In-Reply-To: <11722629943386-git-send-email-normalperson@yhbt.net>
Eric Wong <normalperson@yhbt.net> wrote:
> I chose <F5> because it's also the key to reload the current
> page in web browsers such as Konqueror and Firefox, so users
> are more likely to be familiar with it.
It is also the key for rescan in git-gui. :-)
Though I have to admit, I chose F5 there for the exact reason you
mention above.
--
Shawn.
prev parent reply other threads:[~2007-02-23 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 20:36 [PATCH] gitk: bind <F5> key to Update (reread commits) Eric Wong
2007-02-23 20:41 ` Shawn O. Pearce [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=20070223204113.GA27261@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=normalperson@yhbt.net \
--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.
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).