git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Matt Seitz (matseitz)" <matseitz@cisco.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git send-email should not allow 'y' for in-reply-to
Date: Fri, 11 Jan 2013 16:23:25 -0500	[thread overview]
Message-ID: <20130111212325.GA18193@sigill.intra.peff.net> (raw)
In-Reply-To: <A0DB01D693D8EF439496BC8B037A0AEF322039A7@xmb-rcd-x15.cisco.com>

On Fri, Jan 11, 2013 at 08:13:57PM +0000, Matt Seitz (matseitz) wrote:

> > > How about "What Message-ID to use as In-Reply-To for the first email?"
> > > or "Provide the Message-ID to use as In-Reply-To for the first
> > > email:".
> > 
> > seem fine to me. Maybe somebody who has been confused by it can offer
> > more. At any rate, patches welcome.
> 
> Suggestion: "Message-ID to use as In-Reply-To for the first email:".
> 
> Simple and unlikely to generate a "y" or "n" response.  Putting
> "Message-ID" first makes it more obvious what data is being asked for
> by this prompt.

You'd think. But the existing message that has been causing problems is:

  Message-ID to be used as In-Reply-To for the first email?

which is more or less what you are proposing. I do think a colon rather
than a question mark helps indicate that the response is not yes/no.

-Peff

  reply	other threads:[~2013-01-11 21:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 20:13 git send-email should not allow 'y' for in-reply-to Matt Seitz (matseitz)
2013-01-11 21:23 ` Jeff King [this message]
2013-01-11 21:53   ` Antoine Pelisse
2013-01-11 22:18     ` Junio C Hamano
2013-01-11 22:42       ` Antoine Pelisse
2013-01-11 23:54         ` Junio C Hamano
2013-01-12  1:02           ` Ben Aveling
2013-01-12  2:56             ` Junio C Hamano
     [not found] <1357885869-20815-1-git-send-email-cyliu@suse.com>
     [not found] ` <50EFD066.60501@redhat.com>
2013-01-11 16:39   ` Eric Blake
2013-01-11 16:47     ` Jeff King
2013-01-11 17:51       ` Eric Blake
2013-01-11 18:43       ` Hilco Wijbenga
2013-01-11 18:54         ` Jeff King
2013-02-24  9:03           ` Junio C Hamano

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=20130111212325.GA18193@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=matseitz@cisco.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).