# Re: git send-email should not allow 'y' for in-reply-to 8 messages from 2013-01-11 to 2013-01-12. Participants: Matt Seitz (matseitz), Jeff King, Antoine Pelisse, Junio C Hamano, Ben Aveling. Thread: https://gitlist.dev/t/32597 ## Matt Seitz (matseitz), 2013-01-11 20:13 Subject: Re: git send-email should not allow 'y' for in-reply-to Message-ID: URL: https://gitlist.dev/e/A0DB01D693D8EF439496BC8B037A0AEF322039A7%40xmb-rcd-x15.cisco.com ``` "Jeff King" wrote in message news:<20130111185417.GA12852@sigill.intra.peff.net>... > On Fri, Jan 11, 2013 at 10:43:39AM -0800, Hilco Wijbenga 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. ``` ## Jeff King, 2013-01-11 21:23 Subject: Re: git send-email should not allow 'y' for in-reply-to Message-ID: <20130111212325.GA18193@sigill.intra.peff.net> URL: https://gitlist.dev/e/20130111212325.GA18193%40sigill.intra.peff.net In-Reply-To: ``` 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 ``` ## Antoine Pelisse, 2013-01-11 21:53 Subject: Re: git send-email should not allow 'y' for in-reply-to Message-ID: URL: https://gitlist.dev/e/CALWbr2xasF1y9j3G%3D-fQ9Wwg41Ymv%3DMMsWoqyuhweDov9KpRvg%40mail.gmail.com In-Reply-To: <20130111212325.GA18193@sigill.intra.peff.net> ``` On Fri, Jan 11, 2013 at 10:23 PM, Jeff King wrote: > 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. That is true. I'm definitely not a wording person, but assuming people who make the mistake probably don't read the whole sentence out of laziness (that might be somehow extreme though ;), starting it with "what" makes it obvious at first sight that you can't answer yes/no. That is not true if the message starts with Message-ID .. which doesn't look like a question. Now it feels like you have agree or not. Antoine, ``` ## Junio C Hamano, 2013-01-11 22:18 Subject: Re: git send-email should not allow 'y' for in-reply-to Message-ID: <7vy5fz9xdl.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vy5fz9xdl.fsf%40alter.siamese.dyndns.org In-Reply-To: ``` Antoine Pelisse writes: > On Fri, Jan 11, 2013 at 10:23 PM, Jeff King wrote: >> 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. > > That is true. > > I'm definitely not a wording person, but assuming people who make the > mistake probably don't read the whole sentence out of laziness (that > might be somehow extreme though ;), starting it with "what" makes it > obvious at first sight that you can't answer yes/no. > That is not true if the message starts with Message-ID .. which > doesn't look like a question. Now it feels like you have agree or not. The exchange, when you do not have a configuration, goes like this: $ git send-email 0001-filename-of-the-patch.patch 0001-filename-of-the-patch.patch Who should the emails be sent to (if any)? junio Are you sure you want to use [y/N]? y Message-ID to be used as In-Reply-To for the first email (if any)? Why not do this instead? $ git send-email 0001-filename-of-the-patch.patch 0001-filename-of-the-patch.patch Who should the emails be sent to (if any)? junio Are you sure you want to use [y/N]? y Is this a response to an existing message [y/N]? y What is the Message-ID of the message you are replying to? ``` ## Antoine Pelisse, 2013-01-11 22:42 Subject: Re: git send-email should not allow 'y' for in-reply-to Message-ID: URL: https://gitlist.dev/e/CALWbr2wtAzz7yWb_Z_V0LFt5ddZcRSs7_rea2w%3DghdC847mEyQ%40mail.gmail.com In-Reply-To: <7vy5fz9xdl.fsf@alter.siamese.dyndns.org> ``` On Fri, Jan 11, 2013 at 11:18 PM, Junio C Hamano wrote: > The exchange, when you do not have a configuration, goes like this: > > $ git send-email 0001-filename-of-the-patch.patch > 0001-filename-of-the-patch.patch > Who should the emails be sent to (if any)? junio > Are you sure you want to use [y/N]? y > Message-ID to be used as In-Reply-To for the first email (if any)? > > Why not do this instead? > > $ git send-email 0001-filename-of-the-patch.patch > 0001-filename-of-the-patch.patch > Who should the emails be sent to (if any)? junio > Are you sure you want to use [y/N]? y > Is this a response to an existing message [y/N]? y I'm not sure about the extra question. If the user doesn't care, he will probably use the empty default, which will result in the same number of steps. If the user cares, he probably knows what he's doing and will give a sensible value. > What is the Message-ID of the message you are replying to? I would simply go for: What Message-ID are you replying to (if any)? If I don't know what to answer, I would definitely not say y/yes/n/no, but press enter directly. ``` ## Junio C Hamano, 2013-01-11 23:54 Subject: Re: git send-email should not allow 'y' for in-reply-to Message-ID: <7vmwwf9sx9.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vmwwf9sx9.fsf%40alter.siamese.dyndns.org In-Reply-To: ``` Antoine Pelisse writes: > I would simply go for: > > What Message-ID are you replying to (if any)? > > If I don't know what to answer, I would definitely not say y/yes/n/no, > but press enter directly. Sounds sensible (even though technically you reply to a message that has that message ID, and not to a message ID ;-)). Any better phrasing from others? If not, I'd say we adopt this text. Thanks. ``` ## Ben Aveling, 2013-01-12 01:02 Subject: Re: git send-email should not allow 'y' for in-reply-to Message-ID: <50F0B643.20201@optusnet.com.au> URL: https://gitlist.dev/e/50F0B643.20201%40optusnet.com.au In-Reply-To: <7vmwwf9sx9.fsf@alter.siamese.dyndns.org> ``` On 12/01/2013 10:54 AM, Junio C Hamano wrote: > Antoine Pelisse writes: > >> I would simply go for: >> >> What Message-ID are you replying to (if any)? >> >> If I don't know what to answer, I would definitely not say y/yes/n/no, >> but press enter directly. > Sounds sensible (even though technically you reply to a message > that has that message ID, and not to a message ID ;-)). > > Any better phrasing from others? If not, I'd say we adopt this > text. I guess it depends on how much we mind if people accidentally miss the message ID. If we don't mind much, we could say something like: What Message-ID are you replying to [Default=None]? If we are concerned that when a Message-ID exists, it should be provided, we could split to 2 questions: Are you replying to an existing Message [Y/n]? And then, if the answer is Y, What Message-ID are you replying to? Regards, Ben ``` ## Junio C Hamano, 2013-01-12 02:56 Subject: Re: git send-email should not allow 'y' for in-reply-to Message-ID: <7vd2xb9kjd.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vd2xb9kjd.fsf%40alter.siamese.dyndns.org In-Reply-To: <50F0B643.20201@optusnet.com.au> ``` Ben Aveling writes: > On 12/01/2013 10:54 AM, Junio C Hamano wrote: >> Antoine Pelisse writes: >> >>> I would simply go for: >>> >>> What Message-ID are you replying to (if any)? >>> >>> If I don't know what to answer, I would definitely not say y/yes/n/no, >>> but press enter directly. >> Sounds sensible (even though technically you reply to a message >> that has that message ID, and not to a message ID ;-)). >> >> Any better phrasing from others? If not, I'd say we adopt this >> text. > > I guess it depends on how much we mind if people accidentally miss the > message ID. > > If we don't mind much, we could say something like: > > What Message-ID are you replying to [Default=None]? > > > If we are concerned that when a Message-ID exists, it should be > provided, we could split to 2 questions: > > Are you replying to an existing Message [Y/n]? > > And then, if the answer is Y, > > What Message-ID are you replying to? Eewww. Now we come back to full circles. It sometimes helps to follow the in-reply-to chain to see what has already been said in the thread, I guess ;-) ```