From: Thomas Rast <trast@student.ethz.ch>
To: John Bartholomew <jpa.bartholomew@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: Enhanced git branch list (proposal)
Date: Mon, 23 Jul 2012 20:32:49 +0200 [thread overview]
Message-ID: <87eho2tjji.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <500D954B.4090007@gmail.com> (John Bartholomew's message of "Mon, 23 Jul 2012 19:17:47 +0100")
John Bartholomew <jpa.bartholomew@gmail.com> writes:
> I find the output of `git branch' to be quite bare, and would like to
> see more information; most importantly, what the state of the branch
> is in relation to its upstream.
That is already present: just run git branch -vv.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-07-23 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 18:17 Enhanced git branch list (proposal) John Bartholomew
2012-07-23 18:32 ` Thomas Rast [this message]
2012-07-24 16:40 ` Phil Hord
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=87eho2tjji.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=jpa.bartholomew@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).