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-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.1 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 02FD41F461 for ; Mon, 26 Aug 2019 16:05:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732082AbfHZQFx (ORCPT ); Mon, 26 Aug 2019 12:05:53 -0400 Received: from pb-smtp21.pobox.com ([173.228.157.53]:55796 "EHLO pb-smtp21.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731642AbfHZQFw (ORCPT ); Mon, 26 Aug 2019 12:05:52 -0400 Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id B6F0B6C896; Mon, 26 Aug 2019 12:05:50 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=3UJozcBvvpB5fnZfOIx94kjSacU=; b=FDDDRB o7iMHBekc+geg8kq7weVdMy4f5t+aWnePkvy5489u7deLAKAgVlsRuf/4UxvQ7iM KkLclI3nbKzhHOLqJuv3pYf+7hiCEI9cg+5Xk2KMgajBFkz1TwBRIHa+0aptgdoY xu8SxVRUzTdKbmgJ8ZW2tJJcT4JDitdwJXztI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=LaZy50hFrhqpb9Oo8lD26YYsuWsnNo/Q V15G5Ec/WQwN6ypUQJ7WdWW4TDl6W+Rwuu8ysiNHdQVmkgUMj4xzPloyc19QODSK hhHR3FzDXNqrfBEC0sfzCS8UUQOixHctyGTM2W/ExiaEFo/wcTkN1XHh4ugC3WD1 XfLXsZrwFAA= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id AE9746C895; Mon, 26 Aug 2019 12:05:50 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.76.80.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id D5B176C893; Mon, 26 Aug 2019 12:05:47 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Denton Liu Cc: Philip Oakley , Git Mailing List , =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason , Eric Sunshine Subject: Re: [PATCH v3 13/13] format-patch: learn --infer-cover-subject option References: <20190823181545.GA14048@archbookpro.localdomain> <20190824080328.GA9726@archbookpro.localdomain> Date: Mon, 26 Aug 2019 09:05:45 -0700 In-Reply-To: (Junio C. Hamano's message of "Mon, 26 Aug 2019 07:26:36 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 5E0AB360-C81B-11E9-917C-8D86F504CC47-77302942!pb-smtp21.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Junio C Hamano writes: > Denton Liu writes: > >> Perhaps something like >> --cover-subject-from-description={true,auto,false}? > > Is it still only about "subject"? I thought one of the improved > behaviour was to populate the subject header with the title > (i.e. the first, often single-line, paragraph) and use the remainder > in the body? --use-description-in-cover={both,auto,body} meaning > "both subject and body gets filled" (among the three this name is I > am least happy with), "automatically decide---if the first paragraph > is overly big, it is unwise to use it on the subject", "use it only > in body" (implying "use the *** SUBJECT HERE *** placeholder on the > subject header), perhaps? Ah, I see Philip has suggested "--cover-letter-from-description", which also sounds better by not focusing too much on the 'subject', and I have no strong preference between the two.