Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: Oort Version
Date: 26 Mar 2001 15:29:49 -0500	[thread overview]
Message-ID: <vxkzoe8b7eq.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <vafae68wb1l.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "26 Mar 2001 22:05:42 +0200")

Let me ask something that's been on my mind a while, as long as this
version question has arisen.

What's the Oort cycle for?

About a year ago, or perhaps a year and a half, we had a general round
of wish-list WIBNI thoughts for what should go into Oort after
Pterodactyl was released.  Gnus 5.8 has been out for quite some time,
and we've formally moved into Oort territory, but so far, Oort is just
ongoing bug fixes to 5.8, mostly.

Is there a plan for where Oort is supposed to go?  Is there a goal in
mind?

--karl


  reply	other threads:[~2001-03-26 20:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26 19:00 Jake Colman
2001-03-26 20:05 ` Kai Großjohann
2001-03-26 20:29   ` Karl Kleinpaste [this message]
2001-03-27 21:02     ` Simon Josefsson
2001-03-27 21:33       ` Steven E. Harris
2001-03-27 22:29         ` Robin S. Socha
2001-03-28  0:13           ` Karl Kleinpaste
2001-03-28  0:38             ` Colin Marquardt
2001-03-28 18:06               ` Josh Huber
2001-03-28  3:40             ` Simon Josefsson
2001-03-28 18:51               ` Samuel Padgett
2001-03-28  7:13             ` Christoph Conrad
2001-03-28  7:13             ` Christoph Conrad
2001-03-28  7:15             ` Christoph Conrad
2001-03-28  7:21             ` Christoph Conrad
2001-03-28  8:43               ` Christoph Conrad
2001-03-28 13:59             ` Wizards (was: Re: Oort Version) Per Abrahamsen
2001-03-28 14:47               ` Karl Kleinpaste
2001-03-28 15:58                 ` Per Abrahamsen
2001-03-28 16:34                 ` Paul Jarc
2001-03-28 22:38                 ` Alex Schroeder
2001-03-28 19:03               ` Samuel Padgett

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=vxkzoe8b7eq.fsf@cinnamon.vanillaknot.com \
    --to=karl@charcoal.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;
as well as URLs for NNTP newsgroup(s).