public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tamar Christina <Tamar.Christina@arm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: Backport of patch to gdb 8.0 branch.
Date: Thu, 17 May 2018 19:39:00 -0000	[thread overview]
Message-ID: <20180517171644.7n46a6flnuuz23en@adacore.com> (raw)
In-Reply-To: <HE1PR08MB05406AFA84C5CEB1A5E58DCEFF930@HE1PR08MB0540.eurprd08.prod.outlook.com>

> I'm looking for a backport of
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=957f6b39cab6cac0e4c54e650c7f75109544ac1d
> to the gdb-8.0-branch. The patch allows building with full debug trace
> enabled on AArch64.
> 
> Ok for gdb-8.0-branch?

If not already done so, please create a PR in bugzilla that explains
the problem this patch is fixing. Once this is done, can you add that
PR number to the ChangeLog and revision log of the commit you'd like
to backport?

Here is an example that shows a PR with associated commits:
https://sourceware.org/bugzilla/show_bug.cgi?id=22849

This is to follow part of our procedures aiming at properly documenting
all changes that go into a release branch after we make the first
release on that branch.

-- 
Joel

  parent reply	other threads:[~2018-05-17 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <HE1PR08MB0540BEEB7FDED47D0FE9D6DCFF930@HE1PR08MB0540.eurprd08.prod.outlook.com>
2018-05-16 13:54 ` Tamar Christina
2018-05-17 13:23   ` Tamar Christina
2018-05-17 19:39   ` Joel Brobecker [this message]
2018-05-18 10:57     ` Tamar Christina
2018-05-18 18:50       ` Joel Brobecker

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=20180517171644.7n46a6flnuuz23en@adacore.com \
    --to=brobecker@adacore.com \
    --cc=Tamar.Christina@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).