Gnus development mailing list
 help / color / mirror / Atom feed
From: Sean Doran <smd@ebone.net>
Cc: ding@gnus.org
Subject: Re: ognus
Date: 31 Oct 2000 18:00:03 +0100	[thread overview]
Message-ID: <521ywxkkto.fsf@sean.ebone.net> (raw)
In-Reply-To: <ylem0xtm4b.fsf@windlord.stanford.edu>

Russ Allbery <rra@stanford.edu> writes:

> 5.8.7 has multiple outstanding bugs

In the old days, this would result in a rapid "fixed in zgnus-0.2"
or somesuch if on the developer list (now it's "fixed committed");
if asked somewhere else (e.g. USENET), "will be fixed in gnus-5.8.8".

We do not have Lars (or anyone) doing releasing this
quickly any more, so there are three options, relevant to
other projects which release slowly:

        1. "will be fixed in next Gnus release, don't know when that will be"

        2. "fix pulled up to gnus-5.8.7, grab it by:
           "    a/ applying patches found at <URL>
           "    b/ cvs -d :pserver:gnus@cvs.gnus.org:/usr/local/cvsroot \
           "       checkout gnus -rgnus-5.8.7_patched
           " or if you've done (b) before
           "    c/ cd <path-to-gnus-5.8.7_patched>
           "       cvs update -dP"

        3. "if you're very brave, you can track CVS Gnus"

We seem to be stuck on option three, which is probably the
worst choice for the volunteers who currently do all the
CVS committing and answering questions in various big
venues (e.g. USENET).

There are trade-offs between the first two; one requires
frequent releasing, the other requires policing pull-ups
to the appropriate tag, and storing (in the ftp/www archive)
the pull-ups as patches.

        Sean.



  parent reply	other threads:[~2000-10-31 17:00 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         ` ognus Russ Allbery
2000-10-31 13:06           ` ognus Karl Kleinpaste
2000-10-31 17:00           ` Sean Doran [this message]
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=521ywxkkto.fsf@sean.ebone.net \
    --to=smd@ebone.net \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).