From: "Dave Korn" <dave.korn@artimi.com>
To: "'Bob Rossi'" <bob@brasko.net>, "'Andrew Cagney'" <cagney@gnu.org>
Cc: <gdb@sources.redhat.com>
Subject: RE: gdb 6.4
Date: Wed, 09 Feb 2005 14:59:00 -0000 [thread overview]
Message-ID: <NUTMEGx05lbvTvCv3uS000007fa@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <20050209140252.GA25945@white>
> -----Original Message-----
> From: gdb-owner On Behalf Of Bob Rossi
> Sent: 09 February 2005 14:03
> To: Andrew Cagney
> Cc: gdb@sources.redhat.com
> Subject: Re: gdb 6.4
>
> > I'll be spending the next week ensuring that the patch backlog is
> > drained (I've 260 gdb-patches@ and 80 gdb@ e-mails to clear).
>
> Maybe faster release's is the answer to faster patch review.
>
> Bob Rossi
I don't see how that could be possible. More frequent releases == more time
spent packaging them == less time available to spend reviewing patches == slower
progress on the code, doesn't it?
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-02-09 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 14:03 Andrew Cagney
2005-02-09 14:52 ` Bob Rossi
2005-02-09 14:59 ` Dave Korn [this message]
2005-02-09 14:57 ` Daniel Jacobowitz
2005-02-09 21:27 ` Eli Zaretskii
2005-02-10 2:34 ` Andrew Cagney
2005-02-10 10:30 ` Eli Zaretskii
2005-02-09 19:06 Paul Schlie
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=NUTMEGx05lbvTvCv3uS000007fa@NUTMEG.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=bob@brasko.net \
--cc=cagney@gnu.org \
--cc=gdb@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