git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Maxim Treskin <zerthurd@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: FEATURE REQUEST: Comment assignment on branches
Date: Mon, 15 Mar 2010 22:10:06 +0100	[thread overview]
Message-ID: <4B9EA22E.1010103@lsrfire.ath.cx> (raw)
In-Reply-To: <be8f531d1003150133n3ea64109u7d573dbd533ffa48@mail.gmail.com>

Am 15.03.2010 09:33, schrieb Maxim Treskin:
> Hello
> 
> Is it possible to add comments assignment to branches?
> Something like:
> 
> $ git branch --comment="New branch with implementation of some features" br14
> 
> $ git branch
>   br14
> * master
> 
> $ git branch --comments
>   br14           (New branch with implementation of some features)
> * master
> 
> and when configuration variable branch.comments == true, this behavior
> is default.

Hmm.  You could name your branch
"br14/new-branch-with-implementation-of-some-features" instead of
"br14".  With command line completion you would only have to hit two
extra keys (slash tab) and could enjoy a meaningful branch name everywhere.

René

  reply	other threads:[~2010-03-15 21:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15  8:33 FEATURE REQUEST: Comment assignment on branches Maxim Treskin
2010-03-15 21:10 ` René Scharfe [this message]
2010-03-15 21:32   ` Junio C Hamano
2010-03-16  0:35     ` Mark Lodato
2010-03-16  1:49       ` Junio C Hamano
2010-03-16 14:36   ` Nguyen Thai Ngoc Duy
2010-03-15 21:32 ` Nicolas Sebrecht
2010-03-15 21:34   ` Junio C Hamano
2010-03-16  4:45     ` Miles Bader
2010-03-16  6:03       ` Junio C Hamano
2010-03-16  6:20         ` Miles Bader
2010-03-16  6:26           ` Sverre Rabbelier
2010-03-16  7:33             ` Matthieu Moy

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=4B9EA22E.1010103@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=git@vger.kernel.org \
    --cc=zerthurd@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).