From: Hilco Wijbenga <hilco.wijbenga@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Eric Blake <eblake@redhat.com>,
git@vger.kernel.org, libvir-list@redhat.com
Subject: Re: git send-email should not allow 'y' for in-reply-to
Date: Fri, 11 Jan 2013 10:43:39 -0800 [thread overview]
Message-ID: <CAE1pOi0zc+d6d9Y4KViX24qHgc1WL9atmRuyygorX_DQMj69Hg@mail.gmail.com> (raw)
In-Reply-To: <20130111164730.GA7921@sigill.intra.peff.net>
On 11 January 2013 08:47, Jeff King <peff@peff.net> wrote:
> On Fri, Jan 11, 2013 at 09:39:06AM -0700, Eric Blake wrote:
>
>> > Please don't answer "y" when git send email shows the following prompt:
>> >
>> > "Message-ID to be used as In-Reply-To for the first email?"
>> >
>> > you should respond with a message ID there. Unfortunately we have a
>> > growing thread that contains submissions with this mistake.
<snip/>
> People answer 'y' to "Who should the emails appear to be from?" and
> 'n' to "Message-ID to be used as In-Reply-To for the first email?"
> for some unknown reason. While it is possible that your local
> username really is "y" and you are sending the mail to your local
> colleagues, it is possible, and some might even say it is likely,
> that it is a user error.
I have never used Git's email support so this doesn't affect me one
way or another but it seems that checking the results is fixing the
symptoms, not the problem? I apologize if this was already discussed
but I couldn't find such a discussion.
I was wondering if it might be a better idea to change the wording of
the questions if they have proven so confusing? The first time (just
now) that I read "Message-ID to be used as In-Reply-To for the first
email?", it clearly seemed like a yes/no question to me. :-)
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:". I'm a little surprised that "Who should the emails appear to
be from?" would be interpreted as a yes/no question but we could
rephrase that similarly as "Provide the name of the email sender:" (I
don't really like this particular version but you get the idea).
next prev parent reply other threads:[~2013-01-11 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1357885869-20815-1-git-send-email-cyliu@suse.com>
[not found] ` <50EFD066.60501@redhat.com>
2013-01-11 16:39 ` git send-email should not allow 'y' for in-reply-to Eric Blake
2013-01-11 16:47 ` Jeff King
2013-01-11 17:51 ` Eric Blake
2013-01-11 18:43 ` Hilco Wijbenga [this message]
2013-01-11 18:54 ` Jeff King
2013-02-24 9:03 ` Junio C Hamano
2013-01-11 20:13 Matt Seitz (matseitz)
2013-01-11 21:23 ` Jeff King
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
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAE1pOi0zc+d6d9Y4KViX24qHgc1WL9atmRuyygorX_DQMj69Hg@mail.gmail.com \
--to=hilco.wijbenga@gmail.com \
--cc=eblake@redhat.com \
--cc=git@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).