From: Peter Krefting <peter@softwolves.pp.se>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
David Soria Parra <sn_@gmx.net>, Rotem Yaari <vmalloc@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Feature Request: Branch Annotations
Date: Fri, 10 Oct 2008 09:24:08 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0810100922180.10709@ds9.cixit.se> (raw)
In-Reply-To: <32541b130810081621k32493e20occba9cd97671775d@mail.gmail.com>
Avery Pennarun:
> I guess bash completions would help with this (if you're using bash),
> but even then it's kind of unreasonable to name branches something
> like "bug-111234-widget-performance-improvements-for-customer-x",
> which is the sort of information that would be awfully helpful two
> months later when you're looking at old unmerged branches.
That's exactly what I do for one of the projects I am working on (well,
minus the "bug-" prefix, that's implied). Bash completion works quite
well for that, and the merge commits do give meaningful information.
But I would still like to be able to annotate it. Especially for
long-living bug-fix branches, it could be useful to be able to add
describe a branch with what state it is in, for instance.
--
\\// Peter - http://www.softwolves.pp.se/
prev parent reply other threads:[~2008-10-10 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d2115f4f0810080341m27c4ca9bv9b1e9b66704ef3fa@mail.gmail.com>
[not found] ` <d2115f4f0810080348t62e18b14x1dfe798974332b05@mail.gmail.com>
2008-10-08 10:49 ` Feature Request: Branch Annotations Rotem Yaari
2008-10-08 10:55 ` Thomas Adam
2008-10-08 11:41 ` Baz
2008-10-08 12:08 ` Marc Weber
2008-10-08 13:29 ` David Soria Parra
2008-10-08 23:12 ` Junio C Hamano
2008-10-08 23:20 ` David Soria Parra
2008-10-08 23:21 ` Avery Pennarun
2008-10-09 0:20 ` Miklos Vajna
2008-10-10 8:24 ` Peter Krefting [this message]
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=Pine.LNX.4.64.0810100922180.10709@ds9.cixit.se \
--to=peter@softwolves.pp.se \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sn_@gmx.net \
--cc=vmalloc@gmail.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).