git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baz <brian.ewins@gmail.com>
To: "Thomas Adam" <thomas.adam22@gmail.com>
Cc: "Rotem Yaari" <vmalloc@gmail.com>, git@vger.kernel.org
Subject: Re: Feature Request: Branch Annotations
Date: Wed, 8 Oct 2008 12:41:43 +0100	[thread overview]
Message-ID: <2faad3050810080441sdb1b29bxe92c467c2dd9a908@mail.gmail.com> (raw)
In-Reply-To: <18071eea0810080355g743c7bbfq9d7d39c9a76eb59d@mail.gmail.com>

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?
>
> Wasn't this discussed here before, with a prototype?  ISTR it was, but
> dropped due to lack of interest?  Have a look through the archives.

The most recent thread was 'branch description' back in April, which
discussed alternatives, but petered out:
http://kerneltrap.org/mailarchive/git/2008/4/15/1442684/thread

An older thread on 'topic descriptions' where Junio described his use
of the config file for this:
http://kerneltrap.org/mailarchive/git/2006/12/6/232466/thread

And there's a similar feature in stgit, which uses the same config
setting that Junio did:
http://kerneltrap.org/mailarchive/git/2007/5/14/246358
http://kerneltrap.org/mailarchive/git/2007/4/12/243404

-Baz

>
> -- Thomas Adam
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2008-10-08 11:43 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 [this message]
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

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=2faad3050810080441sdb1b29bxe92c467c2dd9a908@mail.gmail.com \
    --to=brian.ewins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=thomas.adam22@gmail.com \
    --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).