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 6D8FF1F66E for ; Thu, 27 Aug 2020 19:35:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727116AbgH0TfO (ORCPT ); Thu, 27 Aug 2020 15:35:14 -0400 Received: from mail.cmpwn.com ([45.56.77.53]:47670 "EHLO mail.cmpwn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726839AbgH0TfL (ORCPT ); Thu, 27 Aug 2020 15:35:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cmpwn.com; s=cmpwn; t=1598556910; bh=muv9dGwe32jYeFVMiggT0oEEzVaehsAvhdGDo6wh4+A=; h=Cc:Subject:From:To:Date:In-Reply-To; b=KtFEYeRFePVvxl+JwFDXLvT+LySv9AzCRZFjTEd2g+ha8L/BnNiiYx0VcPz76m2y4 Dn8jwOs9EQPx15P4i8ReWQTdJOxb9KH7WAJZ5ajDm4D+Vjww6PXc9DCgMJndkwecGC txUtXfZmULJFU+Fhndi5B+AWCayxgwzvxrOFQZ94= Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Cc: "Drew DeVault" , Subject: Re: [PATCH] send-email: do not prompt for In-Reply-To From: "Drew DeVault" To: "Junio C Hamano" , =?utf-8?q?Carlo_Marcelo_Arenas_Bel=C3=B3n?= Date: Thu, 27 Aug 2020 15:34:38 -0400 Message-Id: In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Do you think this whole workstream could be averted by dropping the $prompting check in the in-reply-to branch? Or would that still constitute a breaking change to user workflows?