From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
Kevin Greiner <kgreiner@compsol.cc>,
emacs-devel@gnu.org, "Kim F. Storm" <no-spam@cua.dk>,
Jason Rumney <jasonr@gnu.org>
Subject: Re: Problem with Gnus
Date: Fri, 22 Oct 2004 19:04:59 +0200 [thread overview]
Message-ID: <v9is92k7k4.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <41792EFE.5070406@compsol.cc> (Kevin Greiner's message of "Fri, 22 Oct 2004 12:02:06 -0400")
On Fri, Oct 22 2004, Kevin Greiner wrote:
> Jason Rumney wrote:
[...]
>>> In order to minimize the inconvenience, I think it's best if I "cvs
>>> add legacy-gnus-agent.el" in Emacs soon (instead of fixing it in
>>> Gnus/v5-10 and waiting for the semi-automatic syncing). I have to
>>> leave now, but I can do it in a couple of hours unless someone has a
>>> better suggestion.
>> Is that really a sensible thing to do?
(The file `legacy-gnus-agent.el' has been added via Miles' arch-sync
before your message, because Kevin has committed it in the v5-10
branch of Gnus.)
>> Now people will have their gnus files upgraded to No Gnus 0.2 even
>> though they are using 5.11. Will this cause problems? Is there a
>> way to undo this if it does?
There might be a problem if someone would move from Gnus 5.11 (Emacs
CVS) to an early version of No Gnus.
>> I'd prefer to hear from Kevin about what he really intended before
>> we do anything that might mess things up even more.
[...]
> Hopefully, yesterday's check-in has resolved all of this.
Gnus works for me, but I don't use the agent.
> The upgrade functions have been re-assigned to v5.11 since that is
> where they are needed.
Hm, as the new agent code is in the v5-10 branch too and we intend to
release 5.10.7 from this branch some day, shouldn't the upgrade
functions be assigned to 5.10.7 *and* we should bump the version in
the v5-10 branch to 5.10.7 [1] now? Else people using the v5-10
branch outside of CVS-Emacs won't get the proper upgrade functions
(though I doubt that many people use this branch).
Lars, WDYT?
Bye, Reiner.
[1] IIRC, usually the version number is increased (in CVS) from 5.10.x
to 5.10.x+1 after the release of 5.10.x. After 5.10.6 this didn't
happen because it jumped to "No Gnus v0.1".
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-10-22 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 15:25 Problem with Gnus Kim F. Storm
2004-10-20 16:42 ` Reiner Steib
2004-10-20 22:24 ` Kevin Greiner
2004-10-21 21:34 ` Jason Rumney
2004-10-22 16:02 ` Kevin Greiner
2004-10-22 17:04 ` Reiner Steib [this message]
2004-10-23 8:43 ` Lars Magne Ingebrigtsen
2004-10-23 13:12 ` Reiner Steib
2004-10-24 16:17 ` Kevin Greiner
2004-11-14 19:49 ` Reiner Steib
2004-11-14 19:53 ` Lars Magne Ingebrigtsen
2004-11-14 21:06 ` Reiner Steib
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v9is92k7k4.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=kgreiner@compsol.cc \
--cc=larsi@gnus.org \
--cc=no-spam@cua.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).