git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lodato <lodatom@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>,
	"Maxim Treskin" <zerthurd@gmail.com>,
	git@vger.kernel.org
Subject: Re: FEATURE REQUEST: Comment assignment on branches
Date: Mon, 15 Mar 2010 20:35:03 -0400	[thread overview]
Message-ID: <ca433831003151735u697c5e3fm431dd98bcf48f7bf@mail.gmail.com> (raw)
In-Reply-To: <7v3a01jmp9.fsf@alter.siamese.dyndns.org>

On Mon, Mar 15, 2010 at 5:32 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> Another thing to worry about is how "--comments" and "-v" would interact
> with each other.

What about putting the comment on the line below, with the same level
of indentation?

  maint    8fcaca3 don't use default revision if a rev was specified
           (preparation for the next maintenance release)
* master   c24138b Merge branch 'sd/format-patch-to'
           (preparation for the next feature release)
  next     0ae494e Merge branch 'pb/log-first-parent-p-m' into next
           (semi-stable test branch for integration into master)

  reply	other threads:[~2010-03-16  0:35 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
2010-03-15 21:32   ` Junio C Hamano
2010-03-16  0:35     ` Mark Lodato [this message]
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=ca433831003151735u697c5e3fm431dd98bcf48f7bf@mail.gmail.com \
    --to=lodatom@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rene.scharfe@lsrfire.ath.cx \
    --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).