From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Joel Reed <jreed@lantekcs.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git branch descriptions
Date: Mon, 10 May 2010 17:08:55 +0200 [thread overview]
Message-ID: <AANLkTin9e0-Zyk1RTpp3hFA0-Wqclabd2JQZAuxd74gG@mail.gmail.com> (raw)
In-Reply-To: <657A681BEF27534399890012B8C8E50E1AD63D1FEA@lcs-exchange01.Lantekcs.com>
Hi,
> I've used git in several jobs now and keep coming back to _really_ wishing I could attach a description to some of my branches. Working on a wide range of topics/branches from week to week and project to project, it's sometimes difficult to quickly remember what each branch is about, without doing a git diff master <branch>. I like to keep branch names short so they're easy to switch to and from, but being able to attach a description that would display when doing a "git branch" would be a huge help.
I think git-notes(1) is the closest thing to what you want.
-- Ram
next prev parent reply other threads:[~2010-05-10 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AcrwUP1AvzllIOBSQwuAO49egMRfdg==>
2010-05-10 14:56 ` git branch descriptions Joel Reed
2010-05-10 15:08 ` Ramkumar Ramachandra [this message]
2010-05-10 23:26 ` Jonathan Nieder
2010-05-11 1:16 ` Geert Bosch
2010-05-11 12:38 ` Joel Reed
2010-05-11 7:44 ` Michael J Gruber
2010-05-11 12:39 ` Joel Reed
2010-05-11 12:33 ` Joel Reed
2010-05-11 12:54 ` Ævar Arnfjörð Bjarmason
2010-05-11 12:58 ` Joel Reed
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=AANLkTin9e0-Zyk1RTpp3hFA0-Wqclabd2JQZAuxd74gG@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=jreed@lantekcs.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).