From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5324 invoked by alias); 1 Mar 2018 17:37:52 -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 5307 invoked by uid 89); 1 Mar 2018 17:37:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx3-rdu2.redhat.com (HELO mx1.redhat.com) (66.187.233.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 01 Mar 2018 17:37:50 +0000 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2D1B77D852; Thu, 1 Mar 2018 17:37:49 +0000 (UTC) Received: from localhost (unused-10-15-17-196.yyz.redhat.com [10.15.17.196]) by smtp.corp.redhat.com (Postfix) with ESMTP id 01AF010B0F24; Thu, 1 Mar 2018 17:37:48 +0000 (UTC) From: Sergio Durigan Junior To: Joel Brobecker Cc: GDB Patches , Simon Marchi , Pedro Alves Subject: Re: [PATCH v3 0/2] Make gdbserver work with filename-only binaries References: <20180210014241.19278-3-sergiodj@redhat.com> <20180228032708.19670-1-sergiodj@redhat.com> <87sh9ka5ze.fsf@redhat.com> <20180301025528.zyh5m5jls45t3ooa@adacore.com> Date: Thu, 01 Mar 2018 17:37:00 -0000 In-Reply-To: <20180301025528.zyh5m5jls45t3ooa@adacore.com> (Joel Brobecker's message of "Thu, 1 Mar 2018 06:55:28 +0400") Message-ID: <87lgfbae8j.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-03/txt/msg00031.txt.bz2 On Wednesday, February 28 2018, Joel Brobecker wrote: >> Simon reminded me that this patch is also a good fit for the 8.1 branch, >> so I went ahead and pushed it there. >> >> 506817a3abd98859eb3474389e756c0253cc28a1 >> 2441702a72f324e41a1624dc042b334f375e2d81 >> 6d607b8812b35ff36fbbad2915696f6669f86a32 > > Thanks for getting this through, Sergio and Simon. > > Just a quick reminder that, now that the .0 is out, all new patches > pushed on the branch should have a corresponding PR number, with > the target milestone set to 8.1. This is to be able to give users > an actionable list of PRs they can look at if they are wondering > what the difference between 8.0 and 8.1 is. Is there one for this > issue? If not, it's good enough to create one after the fact, as > long as the PR points to the various discussions and maybe gives > the SHA1 of the various commits, I think we're good. Hi Joel, Sorry about this, I forgot about the need to create a PR when the release is out. There is no PR for this bug, so I created one following the specifications: https://sourceware.org/bugzilla/show_bug.cgi?id=22907 Please let me know if there's something else I can do. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/