From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: Patch to support Fortran derived type - Revised
Date: Wed, 23 Nov 2005 13:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0511231047360.1579@linux.site> (raw)
In-Reply-To: <20051122162358.GA19024@nevyn.them.org>
On Tue, 22 Nov 2005, Daniel Jacobowitz wrote:
> On Tue, Nov 22, 2005 at 03:47:03PM +0800, Wu Zhou wrote:
> > By the way, anyone has any idea or comments about the patch? I am more
> > than happy to improve it if you have any idea.
> >
> > According to the new maintenance policy, how long should I ping for my
> > un-reviewed patch. If it still gets no reply in a specified time, is
> > there anything I can do to get some attention, escalate this to the SC or
> > anything else?
>
> There is no new policy. It's a proposal, still under discussion. Even
> if it were adopted, escalating to the SC is almost never the right
> thing to do: the SC is completely uninvolved in day-to-day development.
OK. Understand. Hope that this is adopted soon.
> As always, I review code patches as frequently as I am able. I'll get
> to it. If any of the other global maintainers out there want to, of
> course, they're invited to review contributions too!
Thanks! You are really a big help here, for me and also many others I
believe!
Regards
- Wu Zhou
next prev parent reply other threads:[~2005-11-23 2:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 10:35 Wu Zhou
2005-11-16 14:16 ` Eli Zaretskii
2005-11-22 19:21 ` Wu Zhou
2005-11-22 9:36 ` Wu Zhou
2005-11-22 19:20 ` Daniel Jacobowitz
2005-11-23 13:06 ` Wu Zhou [this message]
2005-11-23 2:52 ` Eli Zaretskii
2005-12-08 10:33 ` Daniel Jacobowitz
2005-12-08 14:24 ` Eli Zaretskii
2005-12-08 19:22 ` Daniel Jacobowitz
2005-12-11 17:15 ` Wu Zhou
2005-12-11 23:40 ` Eli Zaretskii
2006-02-20 16:10 ` Daniel Jacobowitz
2006-02-24 7:53 ` Wu Zhou
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=Pine.LNX.4.63.0511231047360.1579@linux.site \
--to=woodzltc@cn.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.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