From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org, Kevin Greiner <kgreiner@compsol.cc>,
"Kim F. Storm" <no-spam@cua.dk>
Subject: Re: Problem with Gnus
Date: Thu, 21 Oct 2004 22:34:51 +0100 [thread overview]
Message-ID: <41782B7B.10305@gnu.org> (raw)
In-Reply-To: <v94qkpl4tc.fsf@marauder.physik.uni-ulm.de>
>Kevin has synched some agent-related bugfixes from the trunk to the
>v5-10 branch. It seems he forgot to install `legacy-gnus-agent.el' in
>the v5-10 branch.
>
>
>
It seems to me he synched too much, since there is code there now to
upgrade the gnus files to a future version. But Kevin will know what he
intended.
>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? 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? I'd prefer to
hear from Kevin about what he really intended before we do anything that
might mess things up even more.
next prev parent reply other threads:[~2004-10-21 21:34 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 [this message]
2004-10-22 16:02 ` Kevin Greiner
2004-10-22 17:04 ` Reiner Steib
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=41782B7B.10305@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kgreiner@compsol.cc \
--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).