Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org, semi-gnus-ja@meadowy.org
Subject: Re: An earnest wish from Semi-gnus people
Date: 10 Apr 2001 12:14:07 +0200	[thread overview]
Message-ID: <iluk84tqcy8.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <yosusnji98ep.fsf@jpl.org.We.hate.spammers> (Katsumi Yamaoka's message of "09 Apr 2001 10:19:42 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> We Semi-gnus people request earnestly that Oort Gnus can handle the
> value of `gnus-newsrc-file-version' which is created by Semi-gnusae
> (T-gnus, Nana-gnus, Semi-gnus, etc.) as such as follows:
> 
> gnus-newsrc-file-version
>  => "T-gnus 6.15.0 r09 (based on Oort Gnus v0.01 ; for SEMI 1.13, FLIM 1.13)"
> 
> Latest Oort Gnus cannot startup with such a value because the function
> `gnus-continuum-version' returns nil for that:

Does it apply to earlier versions of Gnus as well?  Making the fix in
OGnus would only help people that went back to OGnus, but it wouldn't
help people running Gnus 5.7 or 5.9 that comes with Emacs.  So if you
install a semi-gnus you can never go back, unless you go back to OGnus
betas?  (Well, or delete .newsrc.eld...)  To solve that, I think
Semi-gnusae need to be changed to insert a file-version string that
older Gnusae understands.

The same would apply to the use of (I think) `gnus-substring' in
.newsrc.eld, which Larsi-Gnus never has implemented.  So you can't
revert to Larsi-Gnus without defining it... Maybe this is fixed now,
though.



  parent reply	other threads:[~2001-04-10 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09  1:19 Katsumi Yamaoka
2001-04-09  1:55 ` Lars Magne Ingebrigtsen
2001-04-09  2:07   ` Katsumi Yamaoka
2001-04-10 10:14 ` Simon Josefsson [this message]
2001-04-10 13:07   ` Katsumi Yamaoka
2001-04-10 12:59     ` Simon Josefsson

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=iluk84tqcy8.fsf@barbar.josefsson.org \
    --to=simon@josefsson.org \
    --cc=ding@gnus.org \
    --cc=semi-gnus-ja@meadowy.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).