public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Nick Clifton <nickc@redhat.com>, Florian Weimer <fweimer@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: 2.38 branch date approaching
Date: Wed, 12 Jan 2022 10:02:18 -0800	[thread overview]
Message-ID: <CAMe9rOobPsXRVhLBtzuCLjAH8xb5JAe3aACziW8WkyFjs0457w@mail.gmail.com> (raw)
In-Reply-To: <b8a0b127-7d6b-20ce-f8e6-2eaab9bb3748@redhat.com>

On Tue, Jan 4, 2022 at 7:59 AM Nick Clifton via Binutils
<binutils@sourceware.org> wrote:
>
> 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.
>

Hi Nick,

I'd like to fix

https://sourceware.org/bugzilla/show_bug.cgi?id=28743

with

https://sourceware.org/pipermail/binutils/2022-January/119258.html

Thanks.

-- 
H.J.

      parent reply	other threads:[~2022-01-12 18:02 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
2022-01-12 18:02 ` H.J. Lu [this message]

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=CAMe9rOobPsXRVhLBtzuCLjAH8xb5JAe3aACziW8WkyFjs0457w@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).