From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: xml.el - contrib -> lisp ?
Date: Mon, 05 May 2003 21:31:47 +0200 [thread overview]
Message-ID: <plop87y91lkx5o.fsf@gnu-rox.org> (raw)
In-Reply-To: <microsoft-free.87r87efgt2.fsf@eicq.dnsalias.org>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
On 5 mai 2003, Steve Youngs told this:
> gnus-group.el requires nnrss which requires xml, so should we move
> xml.el out of contrib and into lisp?
No. Just add the contrib directory to your load-path and that's
it. What is the real need to have it into the 'official' lisp tree ?
No flame here, just a question of course. I am personaly used to add
the contrib tree into my load-path, so I am just curious about that.
zeDek
--
http://www.gnusfr.org -- French Gnus user site
Anti-war disclaimer:
"Bombing for peace is like fucking for virginity"
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-05-05 19:31 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
2003-05-05 8:39 ` Norbert Koch
2003-05-05 10:00 ` Steve Youngs
2003-05-05 19:31 ` Xavier Maillard [this message]
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=plop87y91lkx5o.fsf@gnu-rox.org \
--to=zedek@gnu-rox.org \
--cc=ding@gnus.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).