git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santhosh Kumar Mani <santhoshmani@gmail.com>
To: Vincent van Ravesteijn <vfr@lyx.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] show tracking branches with their associated branch names
Date: Sat, 10 Dec 2011 16:53:46 +0530	[thread overview]
Message-ID: <1323516226.1698.80.camel@sdesktop> (raw)
In-Reply-To: <4EE32C1B.8070306@lyx.org>

On Sat, 2011-12-10 at 10:53 +0100, Vincent van Ravesteijn wrote:
> Op 10-12-2011 8:40, Santhosh Kumar Mani schreef:
> > The "git branch" command, by default, displays the local branches. There
> > is no visual distinction made between the tracking branches and normal
> > local branches. This patch enables the "git branch" to display
> > tracking info for tracking branches:
> >
> > Before this patch:
> >    $ git branch
> >    * master
> >      local
> >
> > After this patch:
> >    $ git branch
> >    * master [origin/master]
> >      local
> >
> >
> Did you try "git branch -vv" ?
> 

Yes. I did. It is too verbose as it meant to be.

This patch distinguishes between the tracking and non-tracking local
branches.

I use a lot of tracking branches and they track different branches. I
tend find this feature useful to know which branch tracks what.

Of course, I could get this information in different ways. But it makes
sense to have this information displayed by default.

> Vincent

Regards,
Santhosh.

  reply	other threads:[~2011-12-10 11:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10  7:40 [RFC/PATCH] show tracking branches with their associated branch names Santhosh Kumar Mani
2011-12-10  9:53 ` Vincent van Ravesteijn
2011-12-10 11:23   ` Santhosh Kumar Mani [this message]
2011-12-12  7:14     ` Junio C Hamano
2011-12-12 14:19       ` Santhosh

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=1323516226.1698.80.camel@sdesktop \
    --to=santhoshmani@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=vfr@lyx.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 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).