From: Alan Modra <amodra@gmail.com>
To: DJ Delorie <dj@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: IBM long double little-endian
Date: Tue, 20 Aug 2013 22:46:00 -0000 [thread overview]
Message-ID: <20130820224601.GG3430@bubble.grove.modra.org> (raw)
In-Reply-To: <201308201752.r7KHq0iE001780@greed.delorie.com>
On Tue, Aug 20, 2013 at 01:52:00PM -0400, DJ Delorie wrote:
>
> In the future, you can coordinate these types of changes by waiting
> for both approvals and committing to gcc and src simultaneously. You
> don't have to let my scripts copy the patch to src.
I normally do that. This time I attempted to commit to src a minute
or so after the gcc commit and hit "waiting for anoncvs lock", which
persisted for nearly an hour.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2013-08-20 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 0:39 Alan Modra
2013-08-19 7:33 ` Andreas Schwab
2013-08-19 15:53 ` Tom Tromey
2013-08-20 6:45 ` Jan Kratochvil
2013-08-20 6:49 ` Alan Modra
2013-08-20 17:52 ` DJ Delorie
2013-08-20 22:46 ` Alan Modra [this message]
2013-08-21 4:05 ` Tom Tromey
2013-08-21 7:24 ` Andreas Schwab
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=20130820224601.GG3430@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=dj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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