From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Jean-Luc Herren" <jlh@gmx.ch>
Cc: "Jeff King" <peff@peff.net>, "Paul Mackerras" <paulus@samba.org>,
git@vger.kernel.org
Subject: Re: How to make gitk not overwrite my selection?
Date: Thu, 6 Mar 2008 12:00:02 +1300 [thread overview]
Message-ID: <46a038f90803051500w508b3093l7061d44828600a5d@mail.gmail.com> (raw)
In-Reply-To: <47CF223A.60507@gmx.ch>
On Thu, Mar 6, 2008 at 11:44 AM, Jean-Luc Herren <jlh@gmx.ch> wrote:
> Thanks, I don't know tcl either, but the patch seems to work great
> here.
Taking it too here. Welcome option.
m
next prev parent reply other threads:[~2008-03-05 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 15:39 How to make gitk not overwrite my selection? Jean-Luc Herren
2008-03-04 23:03 ` Jeff King
2008-03-05 22:44 ` Jean-Luc Herren
2008-03-05 23:00 ` Martin Langhoff [this message]
2008-03-06 10:34 ` Paul Mackerras
2008-03-06 11:49 ` [PATCH] gitk: make autoselect optional Jeff King
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=46a038f90803051500w508b3093l7061d44828600a5d@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=jlh@gmx.ch \
--cc=paulus@samba.org \
--cc=peff@peff.net \
/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).