From: Howard Miller <howard@e-learndesign.co.uk>
To: Patrick Schoenfeld <schoenfeld@debian.org>
Cc: git@vger.kernel.org
Subject: Re: Feature request: Store comments on branches
Date: Wed, 21 Oct 2009 14:48:20 +0100 [thread overview]
Message-ID: <26ae428a0910210648l11751185mbccbf53f3d467de2@mail.gmail.com> (raw)
In-Reply-To: <20091021133702.GA470@lisa>
2009/10/21 Patrick Schoenfeld <schoenfeld@debian.org>:
> Hi,
>
> I regulary work with various branches, that I call by the number
> of an associated bug tracking / support tracking number. That
> makes it clear to which ticket a given branch belongs.
> In this case I would find it very useful, if I could associate
> short comments with a branch, which would be shown when
> doing a 'git branch'. This way I could see what this branch
> about, without looking up the ticket information.
>
> Obvious the workaround is to name the branches different,
> but this is sometimes not convenient and may result in quiet
> long branch names.
>
> What do others think about this? Would this be useful
> for others, too?
Definitely +1.
Even on a much more simplistic level (and speaking as a relative
newbie) I feel it's an important feature missing. It's terribly easy
in the fog of working on several different projects to remember what
all the branches really are. It is just human nature that you think it
makes perfect sense at the time but in a couple of weeks time you
can't find the branch you want from three or four similar ones. A
comments field for branches would be very helpful.
Howard
next prev parent reply other threads:[~2009-10-21 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 13:37 Feature request: Store comments on branches Patrick Schoenfeld
2009-10-21 13:46 ` Thomas Adam
2009-10-21 13:56 ` B Smith-Mannschott
2009-10-21 14:13 ` Jeff King
2009-10-21 13:48 ` Howard Miller [this message]
2009-10-21 15:05 ` Bill Lear
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=26ae428a0910210648l11751185mbccbf53f3d467de2@mail.gmail.com \
--to=howard@e-learndesign.co.uk \
--cc=git@vger.kernel.org \
--cc=schoenfeld@debian.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).