From: Jedidiah Thompson <wej22007@outlook.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: 2.38 branch date approaching
Date: Wed, 12 Jan 2022 14:48:40 +0000 [thread overview]
Message-ID: <BL0PR02MB4900C240E1F2995E27BE302193529@BL0PR02MB4900.namprd02.prod.outlook.com> (raw)
In-Reply-To: <BL0PR02MB4900962E5F761D6AE7ED248893529@BL0PR02MB4900.namprd02.prod.outlook.com>
Sorry about the duplicate messages. Outlook doesn't play nice with Pipermail
-----Original Message-----
From: Jedidiah Thompson
Sent: Wednesday, January 12, 2022 9:36 AM
To: binutils@sourceware.org
Subject: RE: 2.38 branch date approaching
Not to spam, but would you please review my aarch64-pe patches? I don't want it added to 2.38, as it doesn't have some important features needed (like relocations and DLL support), but it will make it easier for me to work on those features when it gets reviewed.
Thanks
-----Original Message-----
From: Binutils <binutils-bounces+wej22007=outlook.com@sourceware.org> On Behalf Of Nick Clifton via Binutils
Sent: Tuesday, January 4, 2022 10:59 AM
To: Binutils <binutils@sourceware.org>
Subject: 2.38 branch date approaching
Hi Guys,
The time for the 2.38 release is approaching. My schedule currently
looks like this:
Sat Jan 22: Create the 2.38 branch
Sat Jan 29: Create the 2.38 release
It is a short time table because I am trying to get the branch out
before the end of January. These dates can slip if necessary, but
I would prefer to keep them if we can.
Therefore please can anyone with new features that they would like
to see in the next release expedite their patch submissions, and
anyone who is waiting on patch review for their already submitted
patches please ping the relevant maintainers and/or me.
Cheers
Nick
next prev parent reply other threads:[~2022-01-12 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 15:58 Nick Clifton
2022-01-10 16:20 ` H.J. Lu
2022-01-11 5:08 ` Alan Modra
2022-01-12 12:53 ` Jedidiah Thompson
2022-01-12 12:58 ` Jedidiah Thompson
2022-01-13 13:44 ` Nick Clifton
2022-01-13 15:42 ` Jedidiah Thompson
2022-01-12 14:35 ` Jedidiah Thompson
2022-01-12 14:48 ` Jedidiah Thompson [this message]
2022-01-12 18:02 ` H.J. Lu
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=BL0PR02MB4900C240E1F2995E27BE302193529@BL0PR02MB4900.namprd02.prod.outlook.com \
--to=wej22007@outlook.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).