From: Tim Chase <git@tim.thechases.com>
To: git@vger.kernel.org
Subject: branch annotations?
Date: Mon, 25 Nov 2013 08:46:44 -0600 [thread overview]
Message-ID: <20131125084644.350bd4f7@bigbox.christie.dr> (raw)
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
as I currently need to flip back and forth between my git/terminal
and my issue-tracker to know that, if I need to be adding missile
launch codes, I need to be working on QA-31. I know there are "note"
features elsewhere for commits, and I know that git-branch supports
showing the most recent commit (that's not always enough info to
discern the branch's purpose).
Thanks for any ideas on how to ease this pain-point, :-)
-tkc
next reply other threads:[~2013-11-25 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 14:46 Tim Chase [this message]
2013-11-25 14:55 ` branch annotations? Johan Herland
2013-11-25 15:08 ` Tim Chase
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=20131125084644.350bd4f7@bigbox.christie.dr \
--to=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).