From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: xml.el - contrib -> lisp ?
Date: Mon, 05 May 2003 09:35:34 +0200 [thread overview]
Message-ID: <v9llxlu9q1.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <microsoft-free.87r87efgt2.fsf@eicq.dnsalias.org>
On Mon, May 05 2003, Steve Youngs wrote:
> gnus-group.el requires nnrss which requires xml, so should we move
> xml.el out of contrib and into lisp?
`xml.el' comes with Emacs 21.x, so putting it lisp will shadow one
version and may lead to inconsistencies.
Isn't `xml.el' included in one of the packages mentioned in (info
"(gnus)XEmacs")? If not, we should update this node, I guess.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-05-05 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 23:11 Steve Youngs
2003-05-05 7:35 ` Reiner Steib [this message]
2003-05-05 8:39 ` Norbert Koch
2003-05-05 10:00 ` Steve Youngs
2003-05-05 19:31 ` Xavier Maillard
2003-05-05 20:41 ` Xavier Maillard
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=v9llxlu9q1.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).