From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 68923 invoked by alias); 5 Sep 2018 09:58:07 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 68913 invoked by uid 89); 5 Sep 2018 09:58:07 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=reminder X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 05 Sep 2018 09:58:06 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id D54911161AD for ; Wed, 5 Sep 2018 05:58:04 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id j+DSO+BeL7Qr for ; Wed, 5 Sep 2018 05:58:04 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id A611F1161AC for ; Wed, 5 Sep 2018 05:58:04 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id C7FC983A90; Wed, 5 Sep 2018 11:58:02 +0200 (CEST) Date: Wed, 05 Sep 2018 09:58:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: REMINDER about commits on the gdb-8.2-branch Message-ID: <20180905095802.GB9583@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) X-SW-Source: 2018-09/txt/msg00074.txt.bz2 Hello everyone, Just a quick reminder that, following the first release off the gdb-8.2-branch (GDB 8.2), there is now an additional requirement that all commits being pushed to the gdb-8.2-branch much be associated to GDB PR number. That PR number almost must have the Target Milestone field set to GDB 8.2.1. The purpose of this procedure is to better document the changes we make in corrective releases: All the changes made being announced both by email and via the project's web page then reference the GDB PR number (with a corresponding URL), and people wanting to know more about a specific issue can take a look at it in bugzilla. As a positive side-effect, this also helps me save a significant amount of time, not having to evaluate each and every patch that we pushed on that branch, trying to determine what it does, and writing a summary of it. Thank you all! -- Joel