git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] branch: add show-tracking option
Date: Thu, 16 May 2013 09:33:23 -0700	[thread overview]
Message-ID: <7vd2sq7ulo.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAMP44s3cjO4ETd+_oQB=afxDuWZb+HBDEOA2sdHfFQ10+y9foQ@mail.gmail.com> (Felipe Contreras's message of "Thu, 16 May 2013 11:28:45 -0500")

Felipe Contreras <felipe.contreras@gmail.com> writes:

> On Thu, May 16, 2013 at 11:17 AM, Junio C Hamano <gitster@pobox.com> wrote:
>
>> *1* indented because this is dependent of @{u}; showing ahead/behind
>>     without showing @{u} would not make any sense.
>
> That's what 'git branch -v' does.

OK, perhaps people know (or do not have to know) what @{u} is and
find ahead/behind still useful?  In any case, this need to be
separate and independent item, as we would want to be able to
express what we currently show in the updated system.

Thanks for a sanity check.

      parent reply	other threads:[~2013-05-16 16:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  7:48 [PATCH] branch: add show-tracking option Felipe Contreras
2013-05-16  7:51 ` Felipe Contreras
2013-05-16  7:54 ` Duy Nguyen
2013-05-16  7:57   ` Felipe Contreras
2013-05-16  8:00 ` Michael J Gruber
2013-05-16  8:09   ` Felipe Contreras
2013-05-16  8:23     ` Michael J Gruber
2013-05-16  8:23   ` Duy Nguyen
2013-05-16  8:40     ` Michael J Gruber
2013-05-16  8:56       ` Duy Nguyen
2013-05-16 16:17         ` Junio C Hamano
2013-05-16 16:28           ` Felipe Contreras
2013-05-16 16:31             ` Junio C Hamano
2013-05-16 16:33             ` Junio C Hamano [this message]

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=7vd2sq7ulo.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.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).