From: Jeff Sheldon <jeffsheldon@gmail.com>
To: binutils@sourceware.org
Subject: Re: Release 2.23: Ping
Date: Fri, 31 Aug 2012 22:01:00 -0000 [thread overview]
Message-ID: <CAJudumdGJ7K5jC-cRXBj2i95g6Gtk0T2=_y3QyZzsLiCNvro7g@mail.gmail.com> (raw)
On Fri, Aug 31, 2012 at 10:34 AM, Tristan Gingold wrote:
> as far as I understand, aarch64 was committed in the 2.23 branch. I'd like to thanks for doing this timely.
>
> Is there any patch that need to be in the 2.23 release ? Please, reply quickly as I'd like to do the release soon.
If commits are made to master after 2.3 is released, will they be
allowed to go into 2.3.1 or is that reserved strictly for fixes (while
new commits work towards 2.4)?
-Jeff
next reply other threads:[~2012-08-31 20:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 22:01 Jeff Sheldon [this message]
2012-09-03 7:46 ` Tristan Gingold
2012-09-04 1:57 ` Hans-Peter Nilsson
2012-09-04 2:51 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2012-07-23 12:41 Release 2.23 Tristan Gingold
2012-07-31 20:30 ` Matthias Klose
2012-08-01 13:59 ` Tristan Gingold
2012-08-01 14:03 ` Richard Earnshaw
2012-08-01 14:35 ` Tristan Gingold
2012-08-01 14:40 ` Richard Earnshaw
2012-08-02 11:41 ` Tristan Gingold
2012-08-31 14:40 ` Release 2.23: Ping Tristan Gingold
2012-08-31 14:46 ` Jan Beulich
2012-08-31 17:45 ` Tristan Gingold
2012-08-31 18:09 ` Mike Frysinger
2012-09-03 7:51 ` Tristan Gingold
2012-09-04 3:54 ` Mike Frysinger
2012-09-04 13:31 ` Tristan Gingold
2012-09-04 14:20 ` H.J. Lu
2012-09-04 14:31 ` H.J. Lu
2012-09-04 14:37 ` Tristan Gingold
2012-09-04 14:39 ` H.J. Lu
[not found] ` <alpine.DEB.1.10.1208312249380.12630@tp.orcam.me.uk>
2012-09-03 7:50 ` Tristan Gingold
2012-09-03 15:07 ` Maciej W. Rozycki
2012-09-03 15:18 ` Tristan Gingold
2012-09-04 14:45 ` Tristan Gingold
2012-09-04 16:31 ` Maciej W. Rozycki
2012-09-05 0:56 ` Maciej W. Rozycki
2012-09-05 8:54 ` Matthew Gretton-Dann
2012-09-05 9:04 ` Tristan Gingold
2012-09-05 10:59 ` Matthew Gretton-Dann
2012-09-05 12:02 ` Maciej W. Rozycki
2012-09-05 16:50 ` Richard Earnshaw
2012-09-05 20:48 ` Maciej W. Rozycki
2012-09-06 7:14 ` Tristan Gingold
2012-09-18 14:47 ` Maciej W. Rozycki
2012-09-13 17:36 ` Matthias Klose
2012-09-13 18:13 ` Maciej W. Rozycki
2012-09-14 6:58 ` Alan Modra
2012-09-14 8:21 ` Tristan Gingold
2012-09-14 17:05 ` Matthias Klose
2012-09-18 14:44 ` Maciej W. Rozycki
2012-09-03 15:09 ` Maciej W. Rozycki
2012-09-04 13:35 ` Tristan Gingold
2012-09-04 13:42 ` H.J. Lu
2012-09-04 13:51 ` Tristan Gingold
2012-09-04 13:58 ` 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='CAJudumdGJ7K5jC-cRXBj2i95g6Gtk0T2=_y3QyZzsLiCNvro7g@mail.gmail.com' \
--to=jeffsheldon@gmail.com \
--cc=binutils@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).