From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Gnus 5.10 and Emacs' CVS
Date: Fri, 09 Apr 2004 18:13:10 +0200 [thread overview]
Message-ID: <m3oeq19lk9.fsf@defun.localdomain> (raw)
In-Reply-To: <m3y8p59mqf.fsf@fed1.frank-schmitt.net> (Frank Schmitt's message of "Fri, 09 Apr 2004 17:47:52 +0200")
Frank Schmitt <ich@Frank-Schmitt.net> writes:
> Why should Gnus' CVS Head be crippled just because RMS wants it?
Because nobody wants to maintain two different versions of Gnus, or
repeat all of the work of stripping the crypto code every time a Gnus
release is imported to Emacs.
> I mean, if he doesn't want encryption in the version delivered with
> Gnu Emacs, that's OK, but it should stay in the version released
> independent.
The functionality should stay, of course -- maybe move the files to
/contrib. The issue is that we have to separate all of the encryption
functionality cleanly to independent files, so that the rest of Gnus
doesn't depend on them.
--
Jesper Harder <http://purl.org/harder/>
next prev parent reply other threads:[~2004-04-09 16:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 8:53 Frank Schmitt
2004-04-09 10:45 ` Sebastian D.B. Krause
2004-04-10 15:51 ` Kevin Greiner
2004-04-13 11:15 ` Proposed Changes Kevin Greiner
2004-04-13 17:51 ` Reiner Steib
2004-04-14 3:55 ` Kevin Greiner
2004-04-14 6:38 ` Kai Grossjohann
2004-04-14 16:38 ` Kevin Greiner
2004-04-14 20:00 ` Kai Grossjohann
2004-05-16 13:07 ` Lars Magne Ingebrigtsen
2004-05-16 13:53 ` Kai Grossjohann
2004-05-22 17:20 ` Lars Magne Ingebrigtsen
2004-04-09 12:48 ` Gnus 5.10 and Emacs' CVS Jesper Harder
2004-04-09 13:03 ` Henrik Enberg
2004-04-09 13:10 ` Jesper Harder
2004-04-09 15:47 ` Frank Schmitt
2004-04-09 16:13 ` Jesper Harder [this message]
2004-04-09 18:58 ` Peter Lee
2004-04-09 20:09 ` Romain Francoise
2004-04-09 20:34 ` Sebastian D.B. Krause
2004-04-09 21:58 ` Jesper Harder
2004-04-10 2:10 ` Miles Bader
2004-04-09 16:35 ` Henrik Enberg
2004-04-09 16:37 ` Henrik Enberg
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=m3oeq19lk9.fsf@defun.localdomain \
--to=harder@ifa.au.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.
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).