From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.7 required=3.0 tests=AWL,BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_PASS,SPF_PASS,URIBL_BLOCKED shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 62F501F66E for ; Fri, 28 Aug 2020 21:03:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726460AbgH1VDH (ORCPT ); Fri, 28 Aug 2020 17:03:07 -0400 Received: from mail.cmpwn.com ([45.56.77.53]:50298 "EHLO mail.cmpwn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726338AbgH1VDG (ORCPT ); Fri, 28 Aug 2020 17:03:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cmpwn.com; s=cmpwn; t=1598648586; bh=hlF+bXdYNwyrMS2YMDeUl0ivChDCUPOzAJY4/7atgz4=; h=Cc:Subject:From:To:Date:In-Reply-To; b=EoSkSMDYa8GHyCIsOMlFAQ269C/mAwiK7ZqD6ZfurNqDFdzF8zM50SqrJQvB9LN3F gwom9+2TxJspwo0X0muXPbLM0K0yoT3bpFG1ZvYy7ICF6DtmEEa4GRvSr4r1/YwJOA woR8IS81+H7MbfUhhZ4AhkM3dttVra09NyYhe+j8= Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Cc: =?utf-8?q?Carlo_Marcelo_Arenas_Bel=C3=B3n?= , Subject: Re: [PATCH] send-email: do not prompt for In-Reply-To From: "Drew DeVault" To: "Junio C Hamano" Date: Fri, 28 Aug 2020 17:01:46 -0400 Message-Id: In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Fri Aug 28, 2020 at 5:00 PM EDT, Junio C Hamano wrote: > "Drew DeVault" writes: > > > "You can give an empty answer if you are not responding to any message" > > could confuse users, because they might think -v2 is a "response", or > > maybe they've written the patch in response to a discussion on the > > -users mailing list, or any other number of reasons. > > "Type the value you would have given to --in-reply-to command line > option (if you forgot to use it), or leave this field empty" > perhaps? Those who do not know should be able to learn what > "--in-reply-to" is. A prompt help is not the place to do a > documentation. This would be better, yeah, but at that point it's pretty weird, like why are we prompting for this CLI flag and not any others? The answer is just for legacy reasons. There's no inherent justification for it. > > I hate to be a nuisance over such a seemingly simple problem, but there > > are a lot of new users who are struggling here and I care about their > > struggle. What path should we take to fixing this issue for them? > > The ideal way would be to craft step (0) well enough so that new > users trigger the To: prompt in the first place, which would > automatically make the problem disappear ;-) Do you mean teaching users how to use --to upfront? Honestly the prompt seems totally fine to me, there's nothing wrong with a use-case which calls for typing your To address into the prompt. Hell, often I'll use it, or I'll use --annotate and write my To addresses in vim.