From: "Doug Kwan (關振德)" <dougkwan@google.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Binutils <binutils@sourceware.org>, Ian Lance Taylor <iant@google.com>
Subject: Re: Release 2.21 - rough schedule
Date: Tue, 07 Sep 2010 16:38:00 -0000 [thread overview]
Message-ID: <AANLkTi=h8DLPNjFbzLLm9GEMoBRv9xWpCLEd4z6em76L@mail.gmail.com> (raw)
In-Reply-To: <48A902C2-D801-401E-8FC1-3E5179D66B70@adacore.com>
The cortex-a8 workaround in gold is broken. I have a submitted a
patch to Ian but have not heard from him yet.
-Doug
在 2010年9月2日上午7:08，Tristan Gingold <gingold@adacore.com> 寫道：
> Hi,
>
> we are reaching the end of the summer which is the usual time for the release.
>
> I plan to create the branch within the next two weeks. If you have something important to submit, please tell me ASAP.
>
> Once the branch is created, I will wait a few weeks before making the release so that discovered regressions could be put into the branch.
>
> Tristan.
>
>
next prev parent reply other threads:[~2010-09-07 16:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 14:09 Tristan Gingold
2010-09-07 16:38 ` Doug Kwan (關振德) [this message]
2010-09-18 2:59 ` Alan Modra
2010-09-20 15:48 ` Richard Earnshaw
2010-09-21 0:32 ` Alan Modra
2010-09-22 15:22 ` Tejas Belagod
2010-09-22 19:31 ` Richard Sandiford
2010-09-22 22:58 ` Maciej W. Rozycki
2010-09-23 7:17 ` Tristan Gingold
2010-09-23 12:19 ` Maciej W. Rozycki
2010-09-18 7:31 ` Matt Rice
2010-09-21 9:24 ` Mike Frysinger
2010-09-21 9:26 ` Tristan Gingold
2010-09-21 9:28 ` Kai Tietz
2010-09-21 9:31 ` Tristan Gingold
2010-09-21 9:44 ` Kai Tietz
2010-09-23 5:11 ` Dave Korn
2010-09-23 7:33 ` Tristan Gingold
2010-10-21 12:33 ` Release 2.21 - schedule Tristan Gingold
2010-11-03 14:12 ` Release 2.21 - branch on Friday ? Tristan Gingold
2010-11-04 2:40 ` Dave Korn
2010-11-04 8:11 ` Tristan Gingold
2010-11-05 9:24 ` Branch 2.21 created Tristan Gingold
2010-12-08 19:38 ` Andreas Schwab
2010-12-08 23:44 ` Alan Modra
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='AANLkTi=h8DLPNjFbzLLm9GEMoBRv9xWpCLEd4z6em76L@mail.gmail.com' \
--to=dougkwan@google.com \
--cc=binutils@sourceware.org \
--cc=gingold@adacore.com \
--cc=iant@google.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).