From: Tim Chase <git@tim.thechases.com>
To: Johan Herland <johan@herland.net>, <git@vger.kernel.org>
Subject: Re: branch annotations?
Date: Mon, 25 Nov 2013 09:08:45 -0600 [thread overview]
Message-ID: <20131125090845.24ed43e3@bigbox.christie.dr> (raw)
In-Reply-To: <CALKQrgdTxYmy2ncXNB29B0-05g8CK=-jxWfDVPbUjHTPsm1yOw@mail.gmail.com>
On 2013-11-25 15:55, Johan Herland wrote:
> "git branch --edit-description" allows you to write a descriptive
> string for your branch. AFAICS, however, it currently only shows up
> when using request-pull. It does not show up in any git branch
> command. IMHO that should be fixed.
>
> As a workaround, you can use this one-liner:
>
> git for-each-ref --format "%(refname:short)" refs/heads/ | while
> read branch; do echo "$branch - $(git config
> branch.$branch.description)"; done
That works like a charm. Thanks!
-tkc
next prev parent reply other threads:[~2013-11-25 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 14:46 branch annotations? Tim Chase
2013-11-25 14:55 ` Johan Herland
2013-11-25 15:08 ` Tim Chase [this message]
2013-11-25 14:56 ` Jeff King
2013-11-25 18:29 ` Ramkumar Ramachandra
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=20131125090845.24ed43e3@bigbox.christie.dr \
--to=git@tim.thechases.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
/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).