From: Ingo Molnar <mingo@elte.hu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [OT] Your branch is ahead of the tracked remote branch 'origin/master' by 50 commits.
Date: Tue, 1 Jul 2008 12:07:25 +0200 [thread overview]
Message-ID: <20080701100725.GE31309@elte.hu> (raw)
In-Reply-To: <7vlk0mne5d.fsf@gitster.siamese.dyndns.org>
* Junio C Hamano <gitster@pobox.com> wrote:
> Ingo Molnar <mingo@elte.hu> writes:
>
> > i recently switched to 1.5.6.1.89.gd5446 and i'm getting this:
> >
> > Switched to branch "master"
> > Your branch is ahead of the tracked remote branch 'origin/master' by 50 commits.
> >
> > it's a very useful detail! It's especially useful when two branches
> > diverge in a non-trivial way.
> > ...
> > but having a reminder at checkout time is even better (and faster as
> > well). Kudos.
>
> Thanks for a rare positive usability feedback. When I started reading
> your message, I almost expected that I'd hear you say "I am getting
> this useless cruft and it wastes extra cycles."
Git usability is certainly very good. (And what matters even more to me
than absolute usability, Git's usability is improving in a monotonic
way.)
[ You normally only hear from me if i find one of those rare outliers
that confuse me somewhere. So by reading my feedback you must be
getting an impression of problems only - that is far from the truth :) ]
> Somebody must have had a very bright idea that day in late February
> this year.
:)
There's a small detail i was thinking about: is there a way to get this
extra output without actually switching branches? Right now i do this:
earth4:~/tip> git-checkout tip; git-checkout master
Checking out files: 100% (2437/2437), done.
Switched to branch "tip"
Switched to branch "master"
Your branch is ahead of the tracked remote branch 'origin/master' by 50 commits.
(Which is an admitted lame solution but the best i could figure.)
Also, and let me hijack this thread, i sometimes feel adventurous and
try out git/pu for kicks. I tried it two days ago and it was quite OK,
with some fallout:
- the git-dash changes broke half of our scripts around git. (We've got
about 50 tip-* scripts around various git details, about 2200 lines).
I did a mass changeover:
31 files changed, 150 insertions(+), 150 deletions(-)
... and that broke things too - see the two fixes below. I can
understand your desire for a git-dash-less world though, but it's
causing some pain :-) Also, i kept typoing "git-" commands all the time
so i switched back to git/master. Maybe there should be a transition
period where the dash scripts warn if used interactively? Dunno.
[ and there's also a git-rerere Heisenbug i have been fighting with a
lot with git-1.5.5. It's quite hard to reproduce and unfortunately i
cannot create a reproducer: but it resulted in git-rerere confusing
conflict resolutions and putting arch/x86/kernel/process_64.c
postimage entry into the entry for arch/x86/kernel/process_32.c's
postimage file, corrupting the integration run on the _next_ run.
Was there a bug in this area fixed recently that would show up with
such symptoms? The weirdness first showed up when i did a git-rerere
after having done a git-add arch/x86/kernel/process_64.c, git-rerere
printed that it added a new resolution for
arch/x86/kernel/process_32.c. ]
and i like this warning at the end of master/pu make install:
!! You have installed git-* commands to new gitexecdir.
!! Old version git-* commands still remain in bindir.
!! Mixing two versions of Git will lead to problems.
!! Please remove old version commands in bindir now.
that's an easily overlooked detail.
Ingo
--------------->
commit e87616175691dd7154cad049aae2b1bc1385bb7a
Author: Ingo Molnar <mingo@elte.hu>
Date: Mon Jun 30 09:29:36 2008 +0200
- fix more git-dash fallout
Signed-off-by: Ingo Molnar <mingo@elte.hu>
diff --git a/.tip/bin/tip-backup b/.tip/bin/tip-backup
index edd7991..682d68d 100755
--- a/.tip/bin/tip-backup
+++ b/.tip/bin/tip-backup
@@ -7,7 +7,7 @@ check_master
echo "backing up the full -tip repo ..."
mkdir -p ~/tip-backups || exit -1
-FILE=~/tip-backups/tip-git $(get_date_for_tag).tar.bz2
+FILE=~/tip-backups/tip-git-$(get_date_for_tag).tar.bz2
tar cjf $FILE .git || exit -1
commit 1bcce26cf0ba00ea62c051772f66d3e1c616e165
Author: H. Peter Anvin <hpa@zytor.com>
Date: Fri Jun 27 17:05:59 2008 -0700
tip-sync-remote: quote multiword commands in variables
When assigning a multiword command to a variable, it needs to be
quoted.
diff --git a/.tip/bin/tip-sync-remote b/.tip/bin/tip-sync-remote
index 6421e55..aeeb883 100755
--- a/.tip/bin/tip-sync-remote
+++ b/.tip/bin/tip-sync-remote
@@ -65,9 +65,9 @@ do
then
echo "Branch "$B" has local modifications"
echo "Rebasing local modifications to remote"
- CMD=git rebase
+ CMD='git rebase'
else
- CMD=git merge
+ CMD='git merge'
fi
$CMD origin/$B || {
next prev parent reply other threads:[~2008-07-01 10:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 9:13 [OT] Your branch is ahead of the tracked remote branch 'origin/master' by 50 commits Ingo Molnar
2008-07-01 9:26 ` Bruce Stephens
2008-07-01 10:14 ` Ingo Molnar
2008-07-01 11:41 ` SZEDER Gábor
2008-07-01 12:47 ` Jakub Narebski
2008-07-01 19:16 ` Junio C Hamano
2008-07-02 7:50 ` [PATCH 0/3] Making remote tracking statistics available to other tools Junio C Hamano
2008-07-03 16:26 ` Olivier Marin
2008-07-03 19:07 ` Junio C Hamano
2008-07-03 19:25 ` Olivier Marin
2008-07-02 7:51 ` [PATCH 1/3] Refactor "tracking statistics" code used by "git checkout" Junio C Hamano
2008-07-02 7:52 ` [PATCH 2/3] git-status: show the remote tracking statistics Junio C Hamano
2008-07-02 7:52 ` [PATCH 3/3] git-branch -v: " Junio C Hamano
2008-07-02 8:23 ` Johannes Sixt
2008-07-02 8:33 ` Karl Hasselström
2008-07-02 14:44 ` Brian Gernhardt
2008-07-02 8:42 ` Junio C Hamano
2008-07-02 15:44 ` Johannes Schindelin
2008-07-01 12:44 ` [OT] Your branch is ahead of the tracked remote branch 'origin/master' by 50 commits Jakub Narebski
2008-07-01 9:32 ` Junio C Hamano
2008-07-01 10:07 ` Ingo Molnar [this message]
2008-07-01 11:16 ` Miklos Vajna
2008-07-01 11:22 ` Ingo Molnar
2008-07-01 11:41 ` Miklos Vajna
2008-07-01 23:55 ` Junio C Hamano
2008-07-04 8:35 ` Pedro Melo
2008-07-01 12:46 ` Mikael Magnusson
2008-07-01 18:01 ` Björn Steinbrink
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=20080701100725.GE31309@elte.hu \
--to=mingo@elte.hu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).