From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id DC8553857402 for ; Wed, 7 Jul 2021 23:03:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DC8553857402 Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-553-1sGGDhJNM56DS4I7Kp8M-Q-1; Wed, 07 Jul 2021 19:03:29 -0400 X-MC-Unique: 1sGGDhJNM56DS4I7Kp8M-Q-1 Received: by mail-qk1-f200.google.com with SMTP id c17-20020a37e1110000b02903b3a029f1f2so537643qkm.12 for ; Wed, 07 Jul 2021 16:03:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=XxIFBolAEDRvXGL2uGrYe/7ZtcoZy+ydO3QBbwVfbVQ=; b=QJjj23T0JlHAHz10VL9FpHQwbMFPfNQtkGvkip1R/b8TG82T1ctgl5sIzRXhbuQCDe qnKf3rCcWfIdRKgRHgma6Dk6fzJRY9mXBNIteAXrpXAsru7srnGOTBEp6Ok+QuEp9tWF X1pzmGxgqhnAcv5jxw/9DYGlqgOTLhEDM6NfxcFZHZqyPUGxktp8APU+o+Ucvua5pSWb VrBxAjOyfC9Kdw4Zq4sJqYSqxKfLKYz87UTG+HhjCBL5Okns8xA961e7Mha9KEv36Z6B 7m2OsMrTy+Cz0DC1OvjLwddDUKyg+FFOWYnqMrMZZBUyZL95x5pMqYE73h/kJmtrtK7M 55fA== X-Gm-Message-State: AOAM533WVxRdkyuOGjNepWTLuC9rABvrgxALy8S4hfZr+x2/mM9A12P6 Zut83da0yMXFNVPRsJ6GxAGtAdmhIQPbJ35UJGD7+aPxdFZi6TzMzua355EV0FQfu/l/xRQk6zp UYwKt1X8= X-Received: by 2002:ac8:5f8c:: with SMTP id j12mr12834486qta.259.1625699009101; Wed, 07 Jul 2021 16:03:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxeQZcXVFBesGQTRQUvPleC5PPO8GAtmGaPtC66mkEKMkh0Kygpa3ttaXS8bxZKHVaVae1RCw== X-Received: by 2002:ac8:5f8c:: with SMTP id j12mr12834466qta.259.1625699008890; Wed, 07 Jul 2021 16:03:28 -0700 (PDT) Received: from t14s.localdomain (c-73-69-212-193.hsd1.nh.comcast.net. [73.69.212.193]) by smtp.gmail.com with ESMTPSA id x28sm231949qtm.71.2021.07.07.16.03.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 07 Jul 2021 16:03:28 -0700 (PDT) Message-ID: Subject: Re: where is PRnnnn required again? From: David Malcolm To: Martin Sebor , Jonathan Wakely Cc: Marek Polacek , gcc mailing list Date: Wed, 07 Jul 2021 19:03:27 -0400 In-Reply-To: <4be7bb29-c830-05b9-99e5-7e54966d4b5c@gmail.com> References: <9121724e-e741-9bad-a39d-d6ac49422589@gmail.com> <734e36bd-5adb-feed-7e89-d63d233198a4@gmail.com> <4be7bb29-c830-05b9-99e5-7e54966d4b5c@gmail.com> User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00, BODY_8BITS, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2021 23:03:32 -0000 On Wed, 2021-07-07 at 16:58 -0600, Martin Sebor via Gcc wrote: > On 7/7/21 4:24 PM, Jonathan Wakely wrote: > > > > > > On Wed, 7 Jul 2021, 23:18 Martin Sebor, > > wrote: > > > >     On 7/7/21 3:53 PM, Marek Polacek wrote: > >      > I'm not sure why you keep hitting so many issues; git addlog > >     takes care of > >      > this stuff for me and I've had no trouble pushing my > > patches.  Is > >     there > >      > a reason you don't use it also? > > > >     I probably have a completely different workflow.  Git addlog > > isn't > >     a git command (is it some sort of a GCC extension?), and what I > > put > >     in the subject of my emails is almost never the same thing as > > what > >     I put in the commit message. > > > > > > Why not? Why is it useful to write two different explanations of > > the patch? > > Sometimes, maybe.  I don't really think about it too much.  I'm not > the only one who does it.  But what bearing does what we put in > the subject of our patch submissions have on this discussion? FWIW if you use a different subject line for the email as for commit message, it makes it harder to find discussion about the patch in the list archives. > You may have one way of doing things and others another.  Yours may > even be better/more streamlined, I don't know.  That doesn't mean > our tooling should make things more difficult for the the rest of us. > > Martin >