git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Abhijit Menon-Sen <ams@toroid.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make it clear that push can take multiple refspecs
Date: Tue, 29 Jul 2008 23:24:10 -0700	[thread overview]
Message-ID: <7vhca799f9.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080730061727.GA1912@toroid.org> (Abhijit Menon-Sen's message of "Wed, 30 Jul 2008 11:47:27 +0530")

Abhijit Menon-Sen <ams@toroid.org> writes:

> I think it's nice if items in the description exactly match something
> in the synopsis. It gives me more confidence that someone didn't just
> forget to update one or the other.

Yup; queued.  Thanks.

      reply	other threads:[~2008-07-30  6:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 20:09 [PATCH] Make it clear that push can take multiple refspecs Abhijit Menon-Sen
2008-07-29 20:54 ` Junio C Hamano
2008-07-29 21:28   ` Abhijit Menon-Sen
2008-07-29 22:06     ` Junio C Hamano
2008-07-29 23:13       ` Abhijit Menon-Sen
2008-07-29 23:20         ` Junio C Hamano
2008-07-30  6:17           ` Abhijit Menon-Sen
2008-07-30  6:24             ` Junio C Hamano [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=7vhca799f9.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=ams@toroid.org \
    --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).