From: Marc Weber <marco-oweber@gmx.de>
To: git@vger.kernel.org
Subject: Re: Feature Request: Branch Annotations
Date: Wed, 8 Oct 2008 14:08:47 +0200 [thread overview]
Message-ID: <20081008120847.GD9428@gmx.de> (raw)
In-Reply-To: <2faad3050810080441sdb1b29bxe92c467c2dd9a908@mail.gmail.com>
On Wed, Oct 08, 2008 at 12:41:43PM +0100, Baz wrote:
> 2008/10/8 Thomas Adam <thomas.adam22@gmail.com>:
> > 2008/10/8 Rotem Yaari <vmalloc@gmail.com>:
> >> Hi,
> >>
> >> I usually work with many branches in git, each of which represents a
> >> different state of development/stability, but also development tasks
> >> assigned to me.
> >> Sometimes, besides the name of the branch, it could be useful to have
> >> a short description of a branch which quickly reminds me what that
> >> branch is intended for.
> >>
> >> Currently I see no way in git to achieve this (there's a description
> >> for a repository, but not for individual branches).
> >>
> >> Any opinions on this?
[...]
Probably I've missed something. but doesn't top git add some special
files to remember branch relations?
I guess it removes them before merging upstream ?
I would have to reread the README or topGit source to confirm this.
Marc Weber
next prev parent reply other threads:[~2008-10-08 12:10 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 [this message]
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
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=20081008120847.GD9428@gmx.de \
--to=marco-oweber@gmx.de \
--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).