From: Miles Bader <miles@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: encrypt.el
Date: Thu, 21 Oct 2004 19:00:49 -0400 [thread overview]
Message-ID: <20041021230049.GB12964@fencepost> (raw)
In-Reply-To: <4nsm87vrgk.fsf@lifelogs.com>
On Thu, Oct 21, 2004 at 02:47:23PM -0400, Ted Zlatanov wrote:
> > That sounds good. So I would like someone to move encrypt.el into
> > Emacs, and to make this change in it.
>
> I can make this change and add documentation for encrypt.el. I just
> need to know who will import my changes into the Emacs CVS.
You should get Emacs CVS access, but I'm not sure how you do that...
For the actual code changes, just commit changes and new files to the
Gnus v5-10 branch, and I'll make sure they end up in the right place in
Emacs (and perhaps post necessary instructions to this list; lisp/ for
encrypt.el?). [netrc.el is already a common file, so changes to that
should propagate]
For not-in-Gnus changes (NEWS + non-Gnus .texi changes?), you can either
send me diffs, or wait until you have Emacs CVS access.
-Miles
--
Any man who is a triangle, has thee right, when in Cartesian Space, to
have angles, which when summed, come to know more, nor no less, than
nine score degrees, should he so wish. [TEMPLE OV THEE LEMUR]
next prev parent reply other threads:[~2004-10-21 23:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4n7jpu4o7d.fsf@lifelogs.com>
[not found] ` <iluwtxtxis9.fsf@latte.josefsson.org>
2004-10-14 18:37 ` pop3.el itegration with netrc.el Ted Zlatanov
2004-10-14 18:56 ` Simon Josefsson
[not found] ` <v9mzypb0ea.fsf@marauder.physik.uni-ulm.de>
[not found] ` <iluhdoxxgwv.fsf@latte.josefsson.org>
[not found] ` <v94qkx9ix5.fsf@marauder.physik.uni-ulm.de>
[not found] ` <ilu8ya8yleo.fsf@latte.josefsson.org>
[not found] ` <4nis9baoz3.fsf@lifelogs.com>
[not found] ` <v93c0fq2ij.fsf@marauder.physik.uni-ulm.de>
2004-10-15 19:14 ` encrypt.el (was: pop3.el itegration with netrc.el) Ted Zlatanov
2004-10-15 19:41 ` encrypt.el Simon Josefsson
2004-10-16 13:52 ` encrypt.el Richard Stallman
2004-10-18 17:48 ` encrypt.el Ted Zlatanov
2004-10-19 1:28 ` encrypt.el Miles Bader
2004-10-19 1:52 ` encrypt.el Miles Bader
2004-10-19 16:45 ` encrypt.el Richard Stallman
2004-10-21 18:47 ` encrypt.el Ted Zlatanov
2004-10-21 23:00 ` Miles Bader [this message]
2004-10-21 23:05 ` encrypt.el Miles Bader
2004-10-21 23:25 ` encrypt.el Andreas Schwab
2004-10-22 0:35 ` encrypt.el Miles Bader
2004-10-23 4:48 ` encrypt.el Richard Stallman
2004-10-23 10:44 ` encrypt.el Eli Zaretskii
2004-12-01 18:55 ` encrypt.el Ted Zlatanov
2004-12-01 22:05 ` encrypt.el Simon Josefsson
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-12-07 4:24 ` encrypt.el Richard Stallman
2004-12-07 9:42 ` encrypt.el Kim F. Storm
2004-12-08 1:49 ` encrypt.el Miles Bader
2004-12-08 2:49 ` encrypt.el Kenichi Handa
2004-12-08 4:41 ` encrypt.el Richard Stallman
2004-12-03 19:45 encrypt.el Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041021230049.GB12964@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).