From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: pop3.el itegration with netrc.el
Date: Fri, 15 Oct 2004 20:07:00 +0200 [thread overview]
Message-ID: <v93c0fq2ij.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4nis9baoz3.fsf@lifelogs.com>
On Fri, Oct 15 2004, Ted Zlatanov wrote:
> If password.el, netrc.el, encrypt.el, and pop3.el move to Emacs,
> that's OK but I don't have CVS access to Emacs source code so it will
> be harder for me to maintain those files.
netrc.el has already been "moved to Emacs" a long time ago. This
doesn't mean that you cannot maintain the files anymore. Changes in
v5-10/lisp/netrc.el should still be merged into Emacs (follow the URL
for more):
,----[ http://thread.gmane.org/20041010225828.GA31829@fencepost ]
| From: Miles Bader <miles@lsi.nec.co.jp>
| Subject: Re: [rmail-mbox-branch]: mail-utils
| Date: Tue, 12 Oct 2004 11:09:11 +0900
| Message-ID: <buoy8ick7qw.fsf@mctpc71.ucom.lsi.nec.co.jp>
|
| Richard Stallman <rms@gnu.org> writes:
| > Do you mean that a patch from a gnus maintainer would have to be
| > posted to the mailing list to be put into emacs (unlike Gnus
| > changes)?
| >
| > I mean they should treat these files the same way they treat all the
| > other Lisp files that are not part of Gnus. That does not mean ALL
| > changes have to be discussed. They can install local uncontroversial
| > bug fixes without discussion, just as any of us would. However,
| > beyond that, they ought to post on this list.
|
| Ok, that sounds reasonable, and workable in practice for my Gnus-syncing.
`----
password.el and encrypt.el (tla, ...) are new in No Gnus. So these
files will not be considered now, I think.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-10-15 18:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 15:44 Ted Zlatanov
2004-10-14 18:21 ` Simon Josefsson
2004-10-14 18:37 ` Ted Zlatanov
2004-10-14 18:56 ` Simon Josefsson
2004-10-14 18:49 ` Reiner Steib
2004-10-14 19:01 ` Simon Josefsson
2004-10-14 19:52 ` Reiner Steib
2004-10-14 22:39 ` Simon Josefsson
2004-10-15 17:08 ` Ted Zlatanov
2004-10-15 17:43 ` Simon Josefsson
2004-10-15 19:07 ` Ted Zlatanov
2004-10-15 19:16 ` Reiner Steib
2004-10-17 23:13 ` Miles Bader
2004-10-18 18:30 ` Ted Zlatanov
2004-10-21 18:35 ` Ted Zlatanov
2004-10-15 18:07 ` Reiner Steib [this message]
2004-10-15 19:14 ` encrypt.el (was: pop3.el itegration with netrc.el) Ted Zlatanov
[not found] ` <iluwtxrvkfb.fsf@latte.josefsson.org>
[not found] ` <E1CIozF-00034v-V7@fencepost.gnu.org>
[not found] ` <4n4qkrvrwu.fsf@lifelogs.com>
[not found] ` <E1CJx6h-0000Ns-QW@fencepost.gnu.org>
[not found] ` <4nsm87vrgk.fsf@lifelogs.com>
[not found] ` <4nr7m9j1ah.fsf@lifelogs.com>
2004-12-01 22:12 ` encrypt.el Reiner Steib
2004-12-02 16:36 ` encrypt.el Ted Zlatanov
2004-12-02 20:56 ` encrypt.el Reiner Steib
2004-12-07 17:50 ` encrypt.el Ted Zlatanov
2004-10-15 17:48 ` pop3.el itegration with netrc.el Reiner Steib
2004-10-15 17:58 ` Simon Josefsson
2004-10-15 18:55 ` Reiner Steib
2004-10-17 23:22 ` Miles Bader
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=v93c0fq2ij.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--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).