From: richard@tiptree.demon.co.uk
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com, gdb-gnats@sources.redhat.com,
ezannoni@redhat.com, msalter@redhat.com, fnasser@redhat.com,
fedor@gnu.org
Subject: Re: [RFA] ObjC Testsuite
Date: Tue, 04 Mar 2003 06:42:00 -0000 [thread overview]
Message-ID: <8273D87E-4E0C-11D7-97B4-00306544502E@tiptree.demon.co.uk> (raw)
In-Reply-To: <200303031615.h23GFBc26561@duracef.shout.net>
On Monday, March 3, 2003, at 04:15 pm, Michael Elizabeth Chastain
wrote:
>
> Also, this whole review process is getting messy, we are going to have
> several people pushing Adam in different directions. I would like to
> figure out *first* who are going to be the maintainer(s) of
> gdb.objc, and then those people should be the reviewers of this patch.
I've been lurking following this process and trying to figure out
what's going
on, and I wholeheartedly agree that sorting out a few individuals to get
things moving makes sense.
I was getting increasingly worried that, while stuff is being reviewed,
none
of it actually seems to be getting into CVS ... even one of the
earliest patches
to simply add the existing objc code into the configure/make process and
activate it (which I think one reviewer said was a no-brainer or
something
similar) is still outstanding.
I've noticed that the objc patches supplied in the last few months have
already begun to bit-rot.
Surely to avoid that sort of thing, the turnaround between submission
for review and addition to CVS needs to be closer to three days than
three months for most changes. I'm very aware that the sheer number
of patches submitted for review for gdb overall will be putting a lot of
load on reviewers, so hopefully having one or two people making a
particular effort to focus on the ObjC code will help solve this
problem.
Incidentally, I have Adams patches (with some modifications to account
for the recent removal of SYMBOL_NAME) running on debian intel and ppc
successfully, so if I can herlp in any way I'm willing.
next prev parent reply other threads:[~2003-03-04 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 16:15 Michael Elizabeth Chastain
2003-03-04 4:45 ` Adam Fedor
2003-03-04 6:42 ` richard [this message]
2003-03-04 14:54 ` Andrew Cagney
2003-03-05 6:15 ` richard
-- strict thread matches above, loose matches on Subject: below --
2003-02-20 2:19 [RFA]: " Adam Fedor
2003-03-03 2:47 ` Elena Zannoni
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=8273D87E-4E0C-11D7-97B4-00306544502E@tiptree.demon.co.uk \
--to=richard@tiptree.demon.co.uk \
--cc=ezannoni@redhat.com \
--cc=fedor@gnu.org \
--cc=fnasser@redhat.com \
--cc=gdb-gnats@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
--cc=msalter@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