From: Vincent van Ravesteijn <vfr@lyx.org>
To: Santhosh Kumar Mani <santhoshmani@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] show tracking branches with their associated branch names
Date: Sat, 10 Dec 2011 10:53:31 +0100 [thread overview]
Message-ID: <4EE32C1B.8070306@lyx.org> (raw)
In-Reply-To: <1323502829.1698.6.camel@sdesktop>
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" ?
Vincent
next prev parent reply other threads:[~2011-12-10 9:53 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 [this message]
2011-12-10 11:23 ` Santhosh Kumar Mani
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=4EE32C1B.8070306@lyx.org \
--to=vfr@lyx.org \
--cc=git@vger.kernel.org \
--cc=santhoshmani@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).