git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Tim Chase <git@tim.thechases.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>, git@vger.kernel.org
Subject: Re: branch annotations?
Date: Mon, 25 Nov 2013 09:56:44 -0500	[thread overview]
Message-ID: <20131125145644.GB23802@sigill.intra.peff.net> (raw)
In-Reply-To: <20131125084644.350bd4f7@bigbox.christie.dr>

On Mon, Nov 25, 2013 at 08:46:44AM -0600, Tim Chase wrote:

> Is there any way to associate some sort of note with a branch that
> would be shown when listing them?  While I currently have things like
> "issue/QA-42", it would be nice to have a note associated with it so
> I could do something like
> 
>   $ git branch --show-notes
>     issue/CR-88: make sure NoSQL engines support .CSV file backends
>     issue/QA-31: add missile launch codes
>   * issue/QA-42: support flying cars
>     master

There is a "branch description" config entry that you can edit with "git
branch --edit-description" (or by simply tweaking the config file
yourself). However, it is currently only used by git-request-pull when
generating the request.

I think it makes sense to be able to show it as part of "git branch",
but the verbose branch listing there is a bit of a mess. Doing it
cleanly would probably involve refactoring the branch-display code to
allow users to specify more flexible formats.

Ramkumar (cc'd) was looking into that refactoring a while back, but I
did not follow it closely (it looks like some of the underlying
for-each-ref refactoring is on the 'next' branch?).

-Peff

  parent reply	other threads:[~2013-11-25 14:56 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
2013-11-25 14:56 ` Jeff King [this message]
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=20131125145644.GB23802@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=artagnon@gmail.com \
    --cc=git@tim.thechases.com \
    --cc=git@vger.kernel.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).