From: Jonathan Wakely <jwakely@redhat.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: Andrew Haley <aph@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Clarify __atomic_compare_exchange_n docs
Date: Wed, 13 Jan 2016 19:26:00 -0000 [thread overview]
Message-ID: <20160113192618.GO15084@redhat.com> (raw)
In-Reply-To: <56968671.6070305@codesourcery.com>
On 13/01/16 10:16 -0700, Sandra Loosemore wrote:
>On 01/13/2016 07:27 AM, Jonathan Wakely wrote:
>>On 03/10/15 14:00 +0100, Jonathan Wakely wrote:
>>>Here's the latest version of the patch, including the typo fix.
>>
>>Is this patch OK for trunk?
>>
>>The original thread faded out, it's split across two months in the
>>archives:
>>
>>https://gcc.gnu.org/ml/gcc-patches/2015-09/msg02190.html
>>https://gcc.gnu.org/ml/gcc-patches/2015-10/msg00307.html
>>
>>While we might be able to make further improvements I think this is
>>better than what we have now (and I'm hoping not to spend much more
>>on it ;-)
>
>I apologize for losing track of this patch during the previous
>discussion. The version you have now is OK to commit.
No problem, I'd forgotten about it myself until I was clearing out
some local Git branches. It's committed now.
prev parent reply other threads:[~2016-01-13 19:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 12:42 Jonathan Wakely
2015-09-29 16:00 ` Sandra Loosemore
2015-10-01 11:28 ` Andrew Haley
2015-10-01 17:32 ` Jonathan Wakely
2015-10-01 17:34 ` Andrew Haley
2015-10-01 17:42 ` Jonathan Wakely
2015-10-01 17:58 ` Sandra Loosemore
2015-10-01 18:35 ` Jonathan Wakely
2015-10-01 18:40 ` Jonathan Wakely
2015-10-03 13:00 ` Jonathan Wakely
2016-01-13 14:27 ` Jonathan Wakely
2016-01-13 17:16 ` Sandra Loosemore
2016-01-13 19:26 ` Jonathan Wakely [this message]
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=20160113192618.GO15084@redhat.com \
--to=jwakely@redhat.com \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sandra@codesourcery.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).