From: Dara Hazeghi <dhazeghi@yahoo.com>
To: aperez@student.santarosa.edu
Cc: zlaski@apple.com, gcc@gcc.gnu.org
Subject: Re: [objc-improvements-branch] About to start ObjC++
Date: Wed, 21 Jan 2004 00:51:00 -0000 [thread overview]
Message-ID: <20040121005113.577.qmail@web41103.mail.yahoo.com> (raw)
> I actually don't mind the idea of ObjC, although > I
will probably only use it
> minimistically..what I take issue with,
> specifically, is the fact that
> you have carte blanche control over anything
> objc related in GCC, and you
> act like a lord, dictating what will happen and >
when, instead of working with people.
I don't like to butt into threads like this, but what
is the problem here? We explicitly allow developers to
create branches on which they specify the check-in
criteria. We do this precisely for occurrences like
this, to develop or integrate a specific feature.
Would it help us if Zem just sent in a single massive
patch to gcc-patches, and nobody got a chance to
test/comment on the code before it gets reviewed and
merged onto mainline?
In any case, rather than hurling around accusationas,
if there are specific patches/issues you'd like
addressed, perhaps you could specify what they are?
Cheers,
Dara
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
next reply other threads:[~2004-01-21 0:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 0:51 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-20 19:24 Ziemowit Laski
2004-01-20 20:54 ` Alex Perez
2004-01-20 21:44 ` Ziemowit Laski
2004-01-20 21:55 ` Alex Perez
2004-01-20 22:15 ` Ziemowit Laski
2004-01-21 9:34 ` Markus Hitter
2004-01-20 23:34 ` Alexander Malmberg
2004-01-20 23:42 ` Ziemowit Laski
2004-01-21 11:57 ` David Ayers
2004-01-21 15:05 ` steve naroff
2004-01-21 16:16 ` David Ayers
2004-01-21 17:07 ` Pascal J.Bourguignon
2004-01-21 19:43 ` Mike Stump
2004-01-21 23:37 ` Marcel Weiher
2004-01-21 23:58 ` Marcel Weiher
2004-01-21 17:58 ` steve naroff
2004-01-21 20:42 ` Ziemowit Laski
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=20040121005113.577.qmail@web41103.mail.yahoo.com \
--to=dhazeghi@yahoo.com \
--cc=aperez@student.santarosa.edu \
--cc=gcc@gcc.gnu.org \
--cc=zlaski@apple.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).