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=-3.8 required=3.0 tests=AWL,BAYES_00, 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 E6E8E1F461 for ; Mon, 19 Aug 2019 17:29:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728179AbfHSR3k (ORCPT ); Mon, 19 Aug 2019 13:29:40 -0400 Received: from mail-wr1-f67.google.com ([209.85.221.67]:44974 "EHLO mail-wr1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727801AbfHSR3j (ORCPT ); Mon, 19 Aug 2019 13:29:39 -0400 Received: by mail-wr1-f67.google.com with SMTP id p17so9540401wrf.11 for ; Mon, 19 Aug 2019 10:29:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qfMJRD5KSaeUCjdOiDLHzkHW+YhB1TmRSGTYLjXpPRI=; b=hJvgAXBlxsChYyAB7M+ReUSon4Pvxd/KXyp5TuNW6OswDf24js0Zw5e4rbCjP7UfEl TziCKBJAaPY5iZwnTiELVkVdn0pF9v4e9paZLuZ7g6A9EnrE/xZ343fAKsC0EiP/+Y49 MnNqC0rLJUyRLhkm0q/ieSGEvC6/UUIRsUKBopBf+buTEM9/bbN4JUeHq5R3+l+eu/8Y 2nuV+SfA3MEslV8oP9SBy8YvdulGG4ueJLxtUYXx7iJqtL07RR7k85o0gNP12oUPkByA 4P6aRXBoURubcxRbvBtScklBo0fRBt2M7Chw4IqItzr7/eHSWGyl4HBzFAf522xZcvXy cGIQ== X-Gm-Message-State: APjAAAWduNvRLaEw2Dykm/aPK0VCvmWMLRBtAD4Ks/tBtvdZklwQV22I woY7EMXP7jbEiBy6o+2GxtH/yvGuX6CS1rcJ7BE1A8hk X-Google-Smtp-Source: APXvYqydi9ixgHpbCO7Cm+PMNLx4am5MkYt9H4sfA6YZM/VwCKf+0GykfL+DyTcGRSQvnfD1bt8v5hZM/utqINHEuSU= X-Received: by 2002:adf:b60c:: with SMTP id f12mr2680481wre.231.1566235777754; Mon, 19 Aug 2019 10:29:37 -0700 (PDT) MIME-Version: 1.0 References: <5cc5e354b6d84609f3d1de087b3390488abe5343.1566182184.git.liu.denton@gmail.com> In-Reply-To: <5cc5e354b6d84609f3d1de087b3390488abe5343.1566182184.git.liu.denton@gmail.com> From: Eric Sunshine Date: Mon, 19 Aug 2019 13:29:26 -0400 Message-ID: Subject: Re: [PATCH 3/3] format-patch: infer cover letter from branch description To: Denton Liu Cc: Git Mailing List , =?UTF-8?B?w4Z2YXIgQXJuZmrDtnLDsCBCamFybWFzb24=?= , Junio C Hamano Content-Type: text/plain; charset="UTF-8" Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Sun, Aug 18, 2019 at 10:37 PM Denton Liu wrote: > We used to populate the subject of the cover letter generated by > git-format-patch with "*** SUBJECT HERE ***". However, if a user submits > multiple patchsets, they may want to keep a consistent subject between > rerolls. > > If git-format-patch is run with `--infer-cover-letter` or > `format.inferCoverSubject`, infer the subject for the cover letter from > the top line(s) of a branch description, similar to how a subject is > read from a commit message. > > Signed-off-by: Denton Liu > --- > diff --git a/Documentation/config/format.txt b/Documentation/config/format.txt > @@ -36,6 +36,11 @@ format.subjectPrefix:: > +format.inferCoverSubject:: > + A boolean that controls whether or not to infer the subject for > + the cover letter based on the branch's description. See the > + --infer-cover-subject option in linkgit:git-format-patch[1]. What is the default value?