From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: pop3.el itegration with netrc.el
Date: Fri, 15 Oct 2004 19:48:10 +0200 [thread overview]
Message-ID: <v9hdovq3dx.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <ilu8ya8yleo.fsf@latte.josefsson.org>
[ Resending this message. The first one didn't make it to the list,
it seems. At least it's not on Gmane. Sorry for any duplicates. ]
On Fri, Oct 15 2004, Simon Josefsson wrote:
> Done.
Thanks.
> I hope it will be merged automatically to Emacs CVS
When installed in v5-10 (i.e. if it is a bug fix), it should be
automatically synced to Gnus trunk and to Emacs.
> (that gateway is quite neat, btw!).
ACK. Miles also syncs from Emacs to Gnus, but he said that Gnus ->
Emacs is easier for him. I don't know if it is inconvenient for Miles
if we install a change in v5-10 and trunk at the same time.
Maybe we should have MAINTAINANCE file (or README.developer) in Gnus
CVS to explain these non-obvious things, WDYT?
Other items in this file could be:
- ./etc/gnus-news.texi -> make -> GNUS-NEWS
- Avoiding dependencies:
- message / gnus
- nn*
- mm*
- rfc*
- tla netrc pop3 dig dns ...
- Compatibility with XEmacs and older Emacs versions in v5-10 and in
the trunk.
> Perhaps emacs/lisp/gnus/pop3.el should be moved to emacs/lisp/net/?
> People seem to be afraid of using files from gnus/. And now pop3.el
> is standalone. What do you think?
I'd agree. Also for some other files: dig.el dns.el ... If I recall
the discussions on emacs-devel correctly, this implies that the file
would be officially maintained by the Emacs developers. Thus Richard
has to decide about it. Please suggest the moving on emacs-devel.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-10-15 17:48 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
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 ` Reiner Steib [this message]
2004-10-15 17:58 ` pop3.el itegration with netrc.el 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=v9hdovq3dx.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).