From: Benjamin LaHaise <bcrl@redhat.com>
To: "Eric S. Raymond" <esr@thyrsus.com>, linux-kernel@vger.kernel.org
Subject: Re: Penelope builds a kernel
Date: Mon, 14 Jan 2002 18:38:20 -0500 [thread overview]
Message-ID: <20020114183820.G30639@redhat.com> (raw)
In-Reply-To: <20020114165909.A20808@thyrsus.com> <20020114173542.C30639@redhat.com> <20020114173854.C23081@thyrsus.com> <20020114180007.D30639@redhat.com> <20020114180522.A24120@thyrsus.com>
In-Reply-To: <20020114180522.A24120@thyrsus.com>; from esr@thyrsus.com on Mon, Jan 14, 2002 at 06:05:22PM -0500
On Mon, Jan 14, 2002 at 06:05:22PM -0500, Eric S. Raymond wrote:
> Because fetchmail is doing the same thing any other MTA would do in that
> situation -- throwing up its hands, because it doesn't have and can't get
> the information to compensate for the misconfiguration.
Nice cop out. Fetchmail is a hybrid MTA+MUA. Since it straddles the
line, it should follow the rules of least surprise, namely:
1. don't delete a messages without knowing they can be / are
delivered successfully
2. make sure error messages that come from temporary config
issues are sent to the person who can fix them.
FYI, it's easy to fix, just use the correct ordering of download, transmit,
delete that sendmail and other MTAs use. Sendmail doesn't delete a message
out of its spool just because it was sent to the next MTA in the chain,
instead it *waits* for the next MTA to acknowledge the successful receipt
of the message. Funnily, it even fsync()s the spool before acknowledging
incoming messages.
> If you have some magic patch to fix this, I'll take it. If you have
> nothing constructive to contribute, please take your venom elsewhere.
Eric, you're asking kernel developers to trust that you are dealing with
the design issues correctly. Part of that means understanding where the
priorities of the issues that concern you fit in with the rest of the
project. That means understanding what current practice is, and what it
will be to all the players involved (core kernel developers, bleeding edge
users, end users who want a stable system, distro users, distro developers).
So far, I see proof that you are not good at understanding design issues
that don't interest you. This flame war is proof that you're very out of
sync with the rest of the developers. I'm asking you to show some goodwill
by going back and fixing the design issues in your own project in order
to better understand some of the currents at work. Until then, I won't
use fetchmail, and I pity the poor users that do.
-ben
next prev parent reply other threads:[~2002-01-14 23:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 21:59 Penelope builds a kernel Eric S. Raymond
2002-01-14 22:24 ` Jeff Garzik
2002-01-14 22:28 ` Lars Marowsky-Bree
2002-01-14 22:32 ` Davide Libenzi
2002-01-14 22:32 ` Chris Friesen
2002-01-14 22:35 ` Benjamin LaHaise
2002-01-14 22:38 ` Eric S. Raymond
2002-01-14 23:00 ` Benjamin LaHaise
2002-01-14 23:05 ` Eric S. Raymond
2002-01-14 23:38 ` Benjamin LaHaise [this message]
2002-01-15 1:53 ` Eric S. Raymond
2002-01-15 2:36 ` Benjamin LaHaise
2002-01-15 11:53 ` Matthias Andree
2002-01-15 22:32 ` James Antill
2002-01-15 22:28 ` Eric S. Raymond
2002-01-16 1:29 ` Alan Cox
2002-01-15 23:00 ` Diego Calleja
2002-01-14 22:37 ` Bruce Harada
2002-01-15 0:56 ` Thomas Duffy
2002-02-01 20:46 ` Pavel Zaitsev
2002-01-14 22:44 ` Richard Gooch
2002-01-14 22:45 ` Eric S. Raymond
2002-01-14 23:15 ` Richard Gooch
2002-01-15 15:53 ` salvador
2002-01-14 23:08 ` Chris Ricker
2002-01-14 23:14 ` Tom Gilbert
2002-01-15 0:50 ` Nathan Walp
2002-01-15 1:24 ` John Levon
2002-01-15 1:39 ` Tom Rini
2002-01-15 2:07 ` John Levon
2002-01-15 3:59 ` Tom Rini
2002-01-15 13:28 ` David Woodhouse
2002-01-15 19:53 ` Ingo Oeser
2002-01-15 20:37 ` David Woodhouse
2002-01-15 21:00 ` Matthew M
2002-01-16 21:31 ` Felix von Leitner
[not found] <d7.11a4a260.2974c807@aol.com>
2002-01-14 23:51 ` Jeff Garzik
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=20020114183820.G30639@redhat.com \
--to=bcrl@redhat.com \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
/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