From: Carlos O'Donell <carlos@redhat.com>
To: Feng Xue <fxue@os.amperecomputing.com>,
Ramana Radhakrishnan <ramana.gcc@googlemail.com>
Cc: Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>, nd <nd@arm.com>
Subject: Re: glibc 2.29 - Winter is coming...
Date: Wed, 23 Jan 2019 09:07:28 -0500 [thread overview]
Message-ID: <5d49c703-3dde-1175-6230-aed030101c4e@redhat.com> (raw)
In-Reply-To: <BL0PR01MB4593D75E9376CC15EE8CA24AF7990@BL0PR01MB4593.prod.exchangelabs.com>
On 1/23/19 8:40 AM, Feng Xue wrote:
> Now it is still in the stage of code freeze for 2.29 release, is it?
> And once window is opened that I can me to push those patches myself,
> should I need another code-review process on Patchwork?
Yes, master is frozen for the 2.29 release. The release is February 1st.
If the machine maintainers, particularly Szabolcs or Ramana have reviewed
the work and there appears to be consensus that it's correct, then you just
need to wait for the branch to open, Siddhesh will announce this, before
you push your changes.
Please use the ChangeLog as you wrote it with the date adjusted to the day
you commit, use a detailed commit message (that was reviewed as part
of the submission), and remain attentive in the even that your change breaks
something and subsequent rework is needed.
Thank you!
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-01-23 14:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:28 glibc 2.29 - Winter is coming Siddhesh Poyarekar
2019-01-02 10:59 ` Florian Weimer
2019-01-02 11:29 ` Siddhesh Poyarekar
2019-01-02 11:52 ` Rafal Luzynski
2019-01-02 18:24 ` Siddhesh Poyarekar
2019-01-03 0:20 ` Rafal Luzynski
2019-01-03 14:32 ` Carlos O'Donell
2019-01-03 20:58 ` Joseph Myers
2019-01-04 21:25 ` Carlos O'Donell
2019-01-07 18:59 ` Florian Weimer
2019-01-02 13:11 ` Gabriel F. T. Gomes
2019-01-02 13:16 ` Florian Weimer
2019-01-02 13:47 ` Siddhesh Poyarekar
2019-01-02 16:02 ` Gabriel F. T. Gomes
2019-01-08 13:33 ` Szabolcs Nagy
2019-01-08 14:16 ` Carlos O'Donell
2019-01-08 14:21 ` Szabolcs Nagy
2019-01-08 16:50 ` Carlos O'Donell
2019-01-09 10:50 ` Ramana Radhakrishnan
2019-01-09 16:03 ` Carlos O'Donell
[not found] ` <BL0PR01MB4593D75E9376CC15EE8CA24AF7990@BL0PR01MB4593.prod.exchangelabs.com>
2019-01-23 14:07 ` Carlos O'Donell [this message]
2019-01-09 5:48 ` Siddhesh Poyarekar
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d49c703-3dde-1175-6230-aed030101c4e@redhat.com \
--to=carlos@redhat.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=fxue@os.amperecomputing.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=ramana.gcc@googlemail.com \
--cc=siddhesh@gotplt.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).