From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: junkio@cox.net, Olaf Hering <olh@suse.de>, git@vger.kernel.org
Subject: Re: [PATCH] allow double click on current HEAD id after git-pull
Date: Thu, 09 Mar 2006 15:17:29 -0800 [thread overview]
Message-ID: <7vy7zj2oom.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060309210250.GY31278@pasky.or.cz> (Petr Baudis's message of "Thu, 9 Mar 2006 22:02:50 +0100")
Petr Baudis <pasky@suse.cz> writes:
> Dear diary, on Sat, Feb 11, 2006 at 12:26:30PM CET, I got a letter
> where Olaf Hering <olh@suse.de> said that...
>> Double click on to current HEAD commit id is not possible,
>> the dot has to go.
>>
>> olaf@pomegranate:~/kernel/git/linux-2.6> git-pull
>> Unpacking 194 objects
>> 100% (194/194) done
>> * refs/heads/origin: fast forward to branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
>> Updating from 5bc159e6cb7ca8d173195919ee935885c129011e to 25bf368b3d98668c5d5f38e2201d8bca16e52680.
> ^
>
> Junio, is there any particular reason why this hasn't been applied?
Well I kind of like ending a sentence with a full stop. Isn't
this something you can do by confuguiring your cut&paste?
But I do not have a _very_ strong feeling either way. If
majority of the list wants it that way I do not mind.
next prev parent reply other threads:[~2006-03-09 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 11:26 [PATCH] allow double click on current HEAD id after git-pull Olaf Hering
2006-03-09 21:02 ` Petr Baudis
2006-03-09 23:17 ` Junio C Hamano [this message]
2006-03-10 0:25 ` Carl Worth
2006-03-10 0:49 ` Mark Wooding
2006-03-10 1:24 ` Petr Baudis
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=7vy7zj2oom.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=olh@suse.de \
--cc=pasky@suse.cz \
/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).