From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Reiner Steib Newsgroups: gmane.emacs.devel Subject: Re: Problem with Gnus Date: Fri, 22 Oct 2004 19:04:59 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: <41782B7B.10305@gnu.org> <41792EFE.5070406@compsol.cc> Reply-To: Reiner Steib NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1098464815 1032 80.91.229.6 (22 Oct 2004 17:06:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 22 Oct 2004 17:06:55 +0000 (UTC) Cc: Lars Magne Ingebrigtsen , Kevin Greiner , emacs-devel@gnu.org, "Kim F. Storm" , Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 22 19:06:42 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CL2sE-000365-00 for ; Fri, 22 Oct 2004 19:06:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CL2zj-0000Wt-1L for ged-emacs-devel@m.gmane.org; Fri, 22 Oct 2004 13:14:27 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CL2zY-0000Vl-N8 for emacs-devel@gnu.org; Fri, 22 Oct 2004 13:14:16 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CL2zW-0000Ub-Fc for emacs-devel@gnu.org; Fri, 22 Oct 2004 13:14:15 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CL2zW-0000Tc-83 for emacs-devel@gnu.org; Fri, 22 Oct 2004 13:14:14 -0400 Original-Received: from [134.60.1.1] (helo=mail-new.rz.uni-ulm.de) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CL2qg-0000lH-GT; Fri, 22 Oct 2004 13:05:07 -0400 Original-Received: from lumberjack.physik.uni-ulm.de (lumberjack.physik.uni-ulm.de [134.60.10.173]) by mail.uni-ulm.de (8.13.1/8.13.1) with ESMTP id i9MH4xll001219; Fri, 22 Oct 2004 19:05:00 +0200 (MEST) Original-Received: by lumberjack.physik.uni-ulm.de (Postfix, from userid 170) id A5E691810A; Fri, 22 Oct 2004 19:04:59 +0200 (CEST) Mail-Followup-To: Kevin Greiner , Jason Rumney , Kevin Greiner , emacs-devel@gnu.org, "Kim F. Storm" Original-To: Kevin Greiner X-Face: P05mdcZT&lL[-s2=mw~RsllZ0zZAb?vdE}.s (Kevin Greiner's message of "Fri, 22 Oct 2004 12:02:06 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) X-DCC-sonic.net-Metrics: gemini 1156; Body=6 Fuz1=6 Fuz2=6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:28733 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:28733 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/