public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Pinging patches
Date: Tue, 24 Nov 2015 20:44:00 -0000	[thread overview]
Message-ID: <CAMe9rOpu7XEanVZednAtod820QP7Qk0o30KzwAxqeKOTETLDtA@mail.gmail.com> (raw)
In-Reply-To: <5654C1BB.4070501@redhat.com>

On Tue, Nov 24, 2015 at 11:59 AM, Jeff Law <law@redhat.com> wrote:
>
> Just a note to folks, we're well into stage3 in our development cycle right
> now.  Richi, Bernd, Jason, myself and others are working through our queues
> of patches that were submitted before the deadline.
>
> If you are not currently iterating with a maintainer on a patch that was
> submitted before the close of stage1, please ping the patch, including a
> link to the patch in the archives.
>
>
> It's important we wrap up the loose ends and move our focus to bugfixing.
> Speaking strictly  for myself, the bar for what I'll consider will be rising
> daily from now until the release.

FYI, I am planning to ping this patch

https://gcc.gnu.org/ml/gcc-patches/2015-11/msg02791.html

to fix an ABI wrong code and this patch:

https://gcc.gnu.org/ml/gcc-patches/2015-11/msg02605.html

which is a prerequisite for x86 interrupt attribute patch submitted
weeks ago.

-- 
H.J.

  reply	other threads:[~2015-11-24 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 20:01 Jeff Law
2015-11-24 20:44 ` H.J. Lu [this message]
2015-11-24 20:47   ` Jeff Law
2015-11-24 21:01     ` H.J. Lu
2015-11-24 21:01       ` Jeff Law
2015-11-24 22:38         ` 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=CAMe9rOpu7XEanVZednAtod820QP7Qk0o30KzwAxqeKOTETLDtA@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@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).