From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Bruce Stephens <bruce.stephens@isode.com>,
git@vger.kernel.org
Subject: Re: [PATCH 3/3] git-branch -v: show the remote tracking statistics
Date: Wed, 02 Jul 2008 10:23:33 +0200 [thread overview]
Message-ID: <486B3B05.4080006@viscovery.net> (raw)
In-Reply-To: <7vhcb8en92.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
> This teaches "git branch -v" to insert the remote tracking statistics in
> the form of [ours/theirs] just before the one-liner commit log message
> for the branch.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> ... which means that you would see something like this.
>
> * jc/report-tracking 41666f7 [3/117] git-branch -v: show the remo...
>
> I did not think we want to spend extra columns to show the name of
> remote branch each of them tracks, so I am showing only counts.
What makes the "tracking statistics" so useful, is that it explains the
situation in clear words. But here you throw in a few numbers without
explanation. It's practically undiscoverable what the numbers mean.
Therefore, I personally would prefer not to have them here and to save the
space for the commit summary.
What do you think about showing the tracking information only if --track
is supplied? But then even write more information:
* jc/report-tracking 41666f7 diverged 3 vs. 117
foo 1234567 behind 22
bar fedcba9 ahead 6
and filter the output to show only tracking branches.
-- Hannes
next prev parent reply other threads:[~2008-07-02 8:24 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 [this message]
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
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=486B3B05.4080006@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=bruce.stephens@isode.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mingo@elte.hu \
/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).