public inbox for
 help / color / mirror / Atom feed
From: Jakub Jelinek <>
To: David Malcolm <>
Cc: Philip Herron <>,
	gcc Mailing List <>,
Subject: Re: Rust front-end
Date: Tue, 4 Oct 2022 15:04:04 +0200	[thread overview]
Message-ID: <YzwvRK6s1HOXU7ip@tucnak> (raw)
In-Reply-To: <>

On Tue, Oct 04, 2022 at 08:42:58AM -0400, David Malcolm via Gcc wrote:
> On Tue, 2022-10-04 at 13:29 +0100, Philip Herron wrote:
> > Hi everyone,
> > 
> > As the cut-off for merging is coming up in November, quite a few of
> > our patches have not been reviewed yet.
> > 
> > There are a few main issues that have been raised so far, and we are
> > fixing those at the moment in preparation for version 3 of the
> > patches. Is there anything else we can do to make reviewing the rest
> > of the patches easier?
> Do you have a list of which patches need reviewing?
> e.g. perhaps a page showing:
> - which patches are waiting for a reviewer, as opposed to
> - which patches are already approved
> - which patches have issues identified in review
>   - ...where no-one is yet working on addressing them
>   - ...where someone is working on addressing them
> etc
> to make it clearer what the next action is for each patch, and who is
> meant to be taking it.
> (within Red Hat, we used to call this "who has the ball?")

Yeah, our policy in states that
"Pinging patches, Getting patches applied

If you do not receive a response to a patch that you have submitted within
two weeks or so, it may be a good idea to chase it by sending a follow-up
e-mail to the same list(s).  Patches can occasionally fall through the
cracks.  Please be sure to include a brief summary of the patch and the URL
of the entry in the mailing list archive of the original submission."

If some patches have been already reviewed, others partly, others in the
works and others need review, sending a mail with those details
so that it is easy to find out what is still pending is appreciated even


  reply	other threads:[~2022-10-04 13:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 14:51 Philip Herron
2022-06-28  7:30 ` Richard Biener
2022-07-08 17:31   ` Philip Herron
2022-07-11  7:50     ` Richard Biener
2022-07-11 15:01 ` David Edelsohn
2022-10-04 12:29   ` Philip Herron
2022-10-04 12:42     ` David Malcolm
2022-10-04 13:04       ` Jakub Jelinek [this message]
2022-10-05  9:39         ` Philip Herron
2022-10-05  9:36       ` Philip Herron

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YzwvRK6s1HOXU7ip@tucnak \ \ \ \ \ \

* 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).