Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
Subject: Re: ognus
Date: 31 Oct 2000 01:07:16 -0800	[thread overview]
Message-ID: <ylem0xtm4b.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Dave Love's message of "Mon, 30 Oct 2000 23:22:11 GMT"

Dave Love <d.love@dl.ac.uk> writes:

> Certainly things after 5.8.7 don't look too stable and 5.8.7 was
> apparently released with mail-source-delete-incoming turned off, for
> instance, even if there's notthing else seriously wrong with it.

5.8.7 has multiple outstanding bugs, some of which are just annoying
(random failures to decode format=flowed that go away when I peer at them
funny, the random inclusion of NNTP responses in the article headers, some
weird slowness when only a few newsgroups have additional articles when
you press 'g') and some of which seem more serious (complete inability to
encode some corrupted types of messages with non-ASCII characters that I
run into when forwarding spam ranging from a whole sequence of odd
"message has unknown characters" questions to aborting errors about
functions being called with the wrong numbers of arguments).

I've reported some of these to this list.  I tried using the bug-reporting
command and discovered that it included in the e-mail message tons of
information that I consider private, such as my entire split ruleset, so
that was a bit of a non-starter.  Some of the rest I can't reproduce well
enough to generate a bug report for, although I'll give it another try
when I run into a good test case.

> You might think or hope that.  You might hope that everybody with CVS
> write access would have an assignment on file and that no-one else
> checked in anything dubious.  If you were Gerd or me, you'd be
> disappointed and waste a lot of time on the issue.

> rms was right to worry about the situation more than I did previously.

It's staggeringly difficult to run a successful free software project with
many contributors and the GNU copyright submission rules.  I'm very
impressed by those people who manage it; I know from trying to manage INN
development that it would be a complete non-starter for us.  This isn't a
complaint; I know why they exist.  But it's really bloody hard.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



  reply	other threads:[~2000-10-31  9:07 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 22:59 ognus Simon Josefsson
2000-10-28  0:25 ` ognus ShengHuo ZHU
2000-10-28 13:41   ` ognus Simon Josefsson
2000-10-28 15:34     ` ognus Kai Großjohann
2000-10-28 15:41       ` ognus Simon Josefsson
2000-10-29 17:47       ` ognus Dave Love
2000-10-31 22:09     ` S/MIME and PGP/MIME (Was: Re: ognus) Bjørn Mork
2000-10-31 23:18       ` ShengHuo ZHU
2000-11-01 20:41         ` Bjørn Mork
2000-10-28 19:22   ` emacs21-branch (Re: ognus) Karl Eichwalder
2000-10-29 17:47     ` Dave Love
2000-10-29 18:48     ` Karl Eichwalder
2000-10-29 19:50       ` Kai Großjohann
2000-10-29 21:26         ` Florian Weimer
2000-10-29 22:53         ` ShengHuo ZHU
2000-10-30 22:53         ` Dave Love
2000-10-30 23:20           ` Denys Duchier
2000-10-30 23:38             ` Laura Conrad
2000-10-31  9:50               ` Denys Duchier
2000-11-02 17:25                 ` Dave Love
2000-11-02 17:34                   ` Gunnar Evermann
2000-11-03 19:09                     ` Dave Love
2000-11-03 22:07                       ` Gunnar Evermann
2000-11-02 21:01                   ` Denys Duchier
2000-11-02 22:53                     ` Kai Großjohann
2000-11-03 14:31                       ` Per Abrahamsen
2000-11-03 14:42                         ` luis fernandes
2000-11-04 11:42                         ` Steinar Bang
2000-11-04  2:52                       ` Russ Allbery
2000-11-03 19:14                     ` Dave Love
2000-11-03 19:42                       ` Denys Duchier
2000-11-04  0:04                         ` Kai Großjohann
2000-11-04 15:04                         ` Per Abrahamsen
2000-11-04 20:15                           ` Denys Duchier
2000-11-04 22:59                             ` Andreas Fuchs
2000-11-05  1:15                           ` Russ Allbery
2000-11-02 17:23             ` Dave Love
2000-10-31  0:17           ` Steven E. Harris
2000-10-31 10:09           ` Kai Großjohann
2000-10-29 17:39   ` ognus Dave Love
2000-10-30 11:35     ` ognus Per Abrahamsen
2000-10-30 13:05       ` ognus Kai Großjohann
2000-10-30 23:24         ` ognus Dave Love
2000-10-31 10:16           ` ognus Kai Großjohann
2000-11-04 20:23             ` ognus Lars Magne Ingebrigtsen
2000-11-04 22:04               ` ognus Kai Großjohann
2000-11-04 22:34                 ` ognus Lars Magne Ingebrigtsen
2000-10-30 23:22       ` ognus Dave Love
2000-10-31  9:07         ` Russ Allbery [this message]
2000-10-31 13:06           ` ognus Karl Kleinpaste
2000-10-31 17:00           ` ognus Sean Doran
2000-10-31 17:55             ` ognus Kai Großjohann
2000-10-31 13:36         ` ognus Per Abrahamsen
2000-10-31 16:49           ` ognus Sean Doran
2000-11-02 17:35           ` ognus Dave Love
2000-11-02 18:08             ` ognus ShengHuo ZHU
2000-11-02 19:31               ` uunassigned code (was: Re: ognus) Per Abrahamsen
2000-11-03 19:01               ` ognus Dave Love
2000-11-02 19:18             ` ognus Per Abrahamsen
2000-11-02 23:01               ` ognus Kai Großjohann
2000-11-03 14:11                 ` ognus Per Abrahamsen
2000-11-03 19:04               ` ognus Dave Love
2000-11-04 15:11                 ` ognus Per Abrahamsen
2000-11-03 15:39             ` ognus Simon Josefsson
2000-11-04 20:31             ` ognus Lars Magne Ingebrigtsen
2000-10-31 16:37         ` ognus Sean Doran
2000-11-02 17:22           ` ognus Dave Love
2000-11-04 11:48         ` ognus Steinar Bang
2000-11-04 11:45       ` ognus Steinar Bang

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=ylem0xtm4b.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    /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 NNTP newsgroup(s).