From: Zaretskii Eli <ezaretski@elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: RE: [maint] The GDB maintenance process
Date: Tue, 18 Feb 2003 06:08:00 -0000 [thread overview]
Message-ID: <4D19136444628A40840EFE8C5AE04147017A11@ELTIMAIL1.elta.co.il> (raw)
This message was scanned for viruses and other malicious code by PrivaWall.
This mail was sent from ELTA SYS LTD.
> From: Daniel Jacobowitz [mailto:drow@mvista.com]
> Sent: Monday, February 17, 2003 8:07 PM
>
> Right now, we use stricter policies to prevent problems which cause
> breakage. I think these policies are stifling us.
I don't think so. I do agree that some maintainers should try to
review patches in their areas of responsibility more often, but
that doesn't necessarily mean we need to change the
maintenance model.
P.S. Sorry for a possibly messed-up message, this one and
Possibly future ones. We had major changes in our mail
setup, which will take me some time to repair...
This message is processed by the PrivaWall Email Security Server.
next reply other threads:[~2003-02-18 6:08 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 6:08 Zaretskii Eli [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 5:29 Michael Elizabeth Chastain
2003-02-20 20:11 Zaretskii Eli
2003-02-20 20:11 Zaretskii Eli
2003-02-20 14:58 ` Daniel Jacobowitz
2003-02-20 15:56 ` Andrew Cagney
2003-02-20 16:39 ` Andrew Cagney
2003-02-20 15:16 ` Daniel Berlin
2003-02-20 16:19 ` Andrew Cagney
2003-02-20 16:24 ` Daniel Berlin
2003-02-20 16:31 ` Daniel Berlin
2003-02-20 17:13 ` Daniel Berlin
2003-02-22 23:25 ` Eli Zaretskii
2003-02-23 1:57 ` Daniel Berlin
2003-02-23 19:23 ` Eli Zaretskii
2003-02-17 18:07 Daniel Jacobowitz
[not found] ` <drow@mvista.com>
2003-02-17 18:58 ` Kevin Buettner
2003-02-17 21:01 ` Elena Zannoni
2003-02-19 1:49 ` Daniel Jacobowitz
2003-02-19 2:26 ` Joel Brobecker
2003-02-19 15:43 ` Andrew Cagney
2003-02-19 16:29 ` Daniel Jacobowitz
2003-02-19 22:04 ` Andrew Cagney
2003-02-19 13:24 ` Daniel Berlin
2003-02-19 15:51 ` Andrew Cagney
2003-02-19 14:50 ` Andrew Cagney
2003-02-19 17:33 ` David Carlton
2003-02-19 17:57 ` Kevin Buettner
2003-02-19 18:56 ` Andrew Cagney
2003-02-19 20:39 ` Christopher Faylor
2003-02-19 23:17 ` Jason Molenda
2003-02-20 1:53 ` Christopher Faylor
2003-02-19 19:35 ` David Carlton
2003-02-20 18:32 ` Richard Earnshaw
2003-02-22 0:53 ` Andrew Cagney
2003-02-19 15:12 ` Andrew Cagney
2003-02-19 15:21 ` Daniel Jacobowitz
2003-02-19 16:24 ` Andrew Cagney
2003-02-19 18:36 ` Christopher Faylor
2003-02-19 23:36 ` Jason Molenda
2003-02-19 23:52 ` Andrew Cagney
2003-02-19 23:59 ` Jason Molenda
2003-02-20 0:16 ` Elena Zannoni
2003-02-20 0:21 ` Andrew Cagney
2003-02-18 2:39 ` Andrew Cagney
2003-02-18 4:28 ` Andrew Cagney
2003-02-19 3:49 ` Jim Blandy
2003-02-19 16:14 ` Andrew Cagney
2003-02-19 16:31 ` Daniel Jacobowitz
2003-02-19 2:24 ` Jim Blandy
2003-02-19 16:33 ` Andrew Cagney
2003-02-19 22:24 ` Jim Blandy
2003-02-19 22:39 ` Christopher Faylor
2003-02-19 22:53 ` Andrew Cagney
2003-02-19 23:53 ` Elena Zannoni
2003-02-20 1:27 ` Andrew Cagney
2003-02-20 2:48 ` Andrew Cagney
2003-02-21 23:43 ` Andrew Cagney
2003-02-21 23:57 ` Andrew Cagney
2003-02-19 6:05 ` David Carlton
2003-02-23 23:26 ` Mark Kettenis
2003-02-24 7:18 ` Andrew Cagney
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=4D19136444628A40840EFE8C5AE04147017A11@ELTIMAIL1.elta.co.il \
--to=ezaretski@elta.co.il \
--cc=drow@mvista.com \
--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