Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven L Baur <steve@miranova.com>
Subject: Feature Freeze/Red Gnus
Date: 26 Jan 1996 11:09:03 -0800	[thread overview]
Message-ID: <m2hgxieptc.fsf@miranova.com> (raw)

Since September Gnus has an incompatible newsrc format with Gnus
5.1/5.0.13, upgrading is one-way.  Since we already have that hit,
I would suggest that you get the newsrc format the way you want it for
September.  I find it fairly annoying right now that I cannot run Gnus
5 out of my own account, and definitely an inhibition to going in and
tracing down bugs in it ...  Either that, or build
forwards-compatibility in -- which could involve nothing more than
doing something useful with the gnus-newsrc-file-version parameter.

Given how functional/outstanding Gnus' e-mail support is, I'd really
like to see the group information about non-nntp groups moved to a
separate file.  I'd also like to see nntp group information divided
into server-specific and server-independent portions.

-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.


             reply	other threads:[~1996-01-26 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-26 19:09 Steven L Baur [this message]
1996-01-27 20:33 ` Lars Magne Ingebrigtsen
1996-01-28  0:30   ` Steven L Baur
1996-01-30 16:29     ` Lars Magne Ingebrigtsen

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=m2hgxieptc.fsf@miranova.com \
    --to=steve@miranova.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).