From: Olaf Hering <olh@suse.de>
To: git@vger.kernel.org
Subject: [PATCH] allow double click on current HEAD id after git-pull
Date: Sat, 11 Feb 2006 12:26:30 +0100 [thread overview]
Message-ID: <20060211112630.GA12421@suse.de> (raw)
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.
Fast forward
...
olaf@pomegranate:~/kernel/git/linux-2.6> git-whatchanged 5bc159e6cb7ca8d173195919ee935885c129011e..25bf368b3d98668c5d5f38e2201d8bca16e52680.
olaf@pomegranate:~/kernel/git/linux-2.6> git-whatchanged 5bc159e6cb7ca8d173195919ee935885c129011e..25bf368b3d98668c5d5f38e2201d8bca16e52680
<stuff>
Index: git-1.1.3/git-merge.sh
===================================================================
--- git-1.1.3.orig/git-merge.sh
+++ git-1.1.3/git-merge.sh
@@ -127,7 +127,7 @@ case "$#,$common,$no_commit" in
;;
1,"$head",*)
# Again the most common case of merging one remote.
- echo "Updating from $head to $1."
+ echo "Updating from $head to $1"
git-update-index --refresh 2>/dev/null
new_head=$(git-rev-parse --verify "$1^0") &&
git-read-tree -u -m $head "$new_head" &&
Index: git-1.1.3/git-resolve.sh
===================================================================
--- git-1.1.3.orig/git-resolve.sh
+++ git-1.1.3/git-resolve.sh
@@ -41,7 +41,7 @@ case "$common" in
exit 0
;;
"$head")
- echo "Updating from $head to $merge."
+ echo "Updating from $head to $merge"
git-read-tree -u -m $head $merge || exit 1
git-update-ref HEAD "$merge" "$head"
git-diff-tree -p $head $merge | git-apply --stat
--
short story of a lazy sysadmin:
alias appserv=wotan
next reply other threads:[~2006-02-11 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 11:26 Olaf Hering [this message]
2006-03-09 21:02 ` [PATCH] allow double click on current HEAD id after git-pull Petr Baudis
2006-03-09 23:17 ` Junio C Hamano
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=20060211112630.GA12421@suse.de \
--to=olh@suse.de \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.