From: Steve Ellcey <sje@cup.hp.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Tristan Gingold <gingold@adacore.com>,
binutils <binutils@sourceware.org>,
Richard Sandiford <richard.sandiford@linaro.org>
Subject: Re: Release 2.21 - Soon...
Date: Fri, 03 Dec 2010 18:26:00 -0000 [thread overview]
Message-ID: <1291400605.9876.40.camel@hpsje.cup.hp.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1012031806450.4239@tp.orcam.me.uk>
On Fri, 2010-12-03 at 18:08 +0000, Maciej W. Rozycki wrote:
> > I would like to understand what is happening and fix it before 2.21
> > is released.
>
> My December changes are not intended to go into 2.21 and are not on the
> 2.21 branch -- are you seeing the problem with the release branch too?
>
> Maciej
OK, I thought 2.21 was going to be made from ToT. I haven't tried the
release branch but I assume it is OK since it was only around Dec 2 that
I started seeing this problem on the ToT binutils.
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2010-12-03 18:26 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 11:45 Release 2.21 (ready ?) Tristan Gingold
2010-11-19 16:11 ` Doug Kwan (關振德)
2010-11-20 0:02 ` Ian Lance Taylor
2010-11-19 17:10 ` Joel Sherrill
2010-11-23 16:32 ` Release 2.21 - Pre tests Tristan Gingold
2010-11-23 18:54 ` Matthias Klose
2010-11-24 9:28 ` Richard Sandiford
2010-11-24 14:40 ` Matthew Gretton-Dann
2010-11-25 1:40 ` Alan Modra
2010-11-25 9:49 ` Matthew Gretton-Dann
2010-11-25 9:55 ` Tristan Gingold
2010-11-25 15:16 ` Matthew Gretton-Dann
2010-11-23 21:04 ` Ian Lance Taylor
2010-11-23 21:17 ` H.J. Lu
2010-11-23 23:00 ` Ian Lance Taylor
2010-11-23 23:09 ` H.J. Lu
2010-11-24 8:23 ` Tristan Gingold
2010-12-01 0:21 ` Ian Lance Taylor
2010-12-01 11:03 ` Tristan Gingold
2010-12-01 16:53 ` Ian Lance Taylor
2010-12-08 10:47 ` Tristan Gingold
2010-12-08 15:55 ` Ian Lance Taylor
2010-12-08 16:02 ` Tristan Gingold
2010-11-24 9:53 ` Matthew Gretton-Dann
2010-11-24 9:56 ` Tristan Gingold
2010-12-01 15:14 ` Release 2.21 - Soon Tristan Gingold
2010-12-01 15:18 ` H.J. Lu
2010-12-02 15:03 ` Tristan Gingold
2010-12-03 17:43 ` Steve Ellcey
2010-12-03 18:08 ` Maciej W. Rozycki
2010-12-03 18:26 ` Steve Ellcey [this message]
2010-12-04 0:44 ` Maciej W. Rozycki
2010-12-03 21:11 ` Steve Ellcey
2010-12-04 0:55 ` Maciej W. Rozycki
2010-12-06 10:46 ` Chris Smith
2010-12-06 14:02 ` Tristan Gingold
2010-12-06 16:36 ` Steve Ellcey
2010-12-06 17:35 ` Maciej W. Rozycki
2010-12-06 17:40 ` H.J. Lu
2010-12-07 8:24 ` Tristan Gingold
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=1291400605.9876.40.camel@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=binutils@sourceware.org \
--cc=gingold@adacore.com \
--cc=macro@codesourcery.com \
--cc=richard.sandiford@linaro.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).