From: Nick Alcock <nick.alcock@oracle.com>
To: Alan Modra via Binutils <binutils@sourceware.org>
Cc: Alan Modra <amodra@gmail.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH toplevel] libctf: new testsuite
Date: Wed, 06 Jan 2021 11:48:33 +0000 [thread overview]
Message-ID: <87ble2mgku.fsf@esperi.org.uk> (raw)
In-Reply-To: <20210105225340.GG13873@bubble.grove.modra.org> (Alan Modra via Binutils's message of "Wed, 6 Jan 2021 09:23:40 +1030")
On 5 Jan 2021, Alan Modra via Binutils told this:
> It doesn't apply due to gcc missing binutils 87279e3cef5b2c5 changes
> too. I could fix that easily enough but I'm going to ask that you
> post a combined patch to bring the gcc repo up to date with any libctf
> changes.
Oops! That never occurred to me, but of course all the earlier stuff is
probably missing too. Will come up with one once I've properly woken up.
(Sorry, I really should have tried to apply it :( )
--
NULL && (void)
next prev parent reply other threads:[~2021-01-06 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 15:25 Nick Alcock
2021-01-05 22:53 ` Alan Modra
2021-01-06 11:48 ` Nick Alcock [this message]
2021-01-06 13:18 ` [PATCH v2 toplevel] sync libctf toplevel from binutils-gdb Nick Alcock
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=87ble2mgku.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
/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).