Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Roland McGrath <mcgrathr@google.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: [PATCH users/roland/osabi-assert] Do not crash on unrecognized GNU .note.ABI-tag values
Date: Fri, 29 May 2015 17:00:00 -0000	[thread overview]
Message-ID: <55689B25.804@redhat.com> (raw)
In-Reply-To: <CAB=4xhoNhJbN5naaZQR4k4e=zAD7TyfPF7OG7damoDp8ChatGA@mail.gmail.com>

On 05/29/2015 05:32 PM, Roland McGrath wrote:
> On Fri, May 29, 2015 at 3:07 AM, Pedro Alves <palves@redhat.com> wrote:
>> In order to get this into a release branch, the protocol is to file
>> a PR and then once fixed, list the fix in the release page in the wiki:
>>
>>   https://sourceware.org/gdb/wiki/GDB_7.9_Release
>>
>> That helps the release manager build the release notes.
> 
> I've filed 18464 for it.

Thanks.

> I'm not clear from what you said here whether I
> should cherry-pick the commit onto the branch myself, or just list it in
> the "Maybe" section on the wiki to wait for approval.

I've added a new "Fixes in the GDB 7.9 branch" in case there's
another release.  Please push to the branch and list under "Done".

> Below is what I've committed to the trunk.
> Can I cherry-pick it to the 7.9 branch too?

Go ahead.

Thanks,
Pedro Alves


  reply	other threads:[~2015-05-29 17:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  0:21 Roland McGrath
2015-05-29 10:07 ` Pedro Alves
2015-05-29 16:26   ` Doug Evans
2015-05-29 16:29     ` Pedro Alves
2015-05-29 16:32   ` Roland McGrath
2015-05-29 17:00     ` Pedro Alves [this message]
2015-05-29 17:34       ` Roland McGrath
2015-05-29 17:36         ` Pedro Alves
2015-05-29 18:21           ` Roland McGrath
2015-05-29 18:24             ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55689B25.804@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mcgrathr@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox