From: Basile Starynkevitch <basile@starynkevitch.net>
To: gcc@gcc.gnu.org
Cc: jeremie.salvucci@free.fr, dnovillo@google.com, iant@google.com,
bonzini@gnu.org, laurynas.biveinis@gmail.com,
Ralf.Wildenhues@gmx.de
Subject: who can & want to review gengtype patches?
Date: Tue, 07 Sep 2010 08:42:00 -0000 [thread overview]
Message-ID: <20100907104154.ab8dd486.basile@starynkevitch.net> (raw)
Hello All,
We (= Basile Starynkevitch + Jeremie Salvucci) have worked on improving gengtype, notably for plugins (the state of gengtype after having parsed all the files is persisted and may be re-used by plugins using GTY without requiring availability of GCC source & build tree.). We also added some other improvements into gengtype.
Laurynas Beveinis kindly took time to review our first set of patches. http://gcc.gnu.org/ml/gcc-patches/2010-09/msg00421.html http://gcc.gnu.org/ml/gcc-patches/2010-09/msg00420.html etc. Some other people, in particular Paolo Bonzini & Ralf Wildenhues, kindly gave comments on minor points (e.g. Makefile.in).
However, I cannot understand who is officially able to OK our patch to gengtype & is willing to take some time to review our patch (I will send an improved & completed version of our patch set very soon, addressing every comment we got so far).
The words gengtype, GTY, garbage do not seem to appear the MAINTAINERS file, so it seems that gengtype & GTY don't have any specialized reviewers.
And gengtype is not a very well written and easy to maintain piece of code, at least in our opinion.
Do we have any chance to have our patch set reviewed (by a person authorised to OK it) and accepted before end of the stage 1 of current trunk 4.6?
With whom should I interact about our gengtype work, and who is authorized to OK it (and have sufficient time to help)?
Cheers!
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***
next reply other threads:[~2010-09-07 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 8:42 Basile Starynkevitch [this message]
2010-09-07 8:47 ` Paolo Bonzini
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=20100907104154.ab8dd486.basile@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bonzini@gnu.org \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=jeremie.salvucci@free.fr \
--cc=laurynas.biveinis@gmail.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).