Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: ding@gnus.org
Subject: emacs->gnus merge questions
Date: Sat, 08 Dec 2007 12:24:39 +0900	[thread overview]
Message-ID: <874petkgw8.fsf@catnip.gol.com> (raw)

I'm doing the back-merge from the Emacs trunk to the Gnus trunk.

There are some changes which may or may not be appropriate for Gnus:

(1) deleted:  encrypt.el
(2) deleted:  assistant.el
(3) rename:   password.el => password-cache.el

I'm inclined to include all these changes (the fewer differences between
Gnus and Gnus-in-Emacs, the better); does anyone have a comment?

In addition, uses of `declare-function' have been added to various
files.  I assume a Gnus maintainer will want to replace this with a
gnus-specific macro for backwards compatibility.

-Miles

-- 
((lambda (x) (list x x)) (lambda (x) (list x x)))



             reply	other threads:[~2007-12-08  3:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08  3:24 Miles Bader [this message]
2007-12-08 19:38 ` Reiner Steib
2007-12-08 21:19   ` Miles Bader
2007-12-08 21:29     ` Reiner Steib
2007-12-08 23:32   ` Miles Bader
2007-12-08 23:45   ` Miles Bader
2008-02-16 13:24     ` encrypt.el (was: emacs->gnus merge questions) Reiner Steib
2008-02-16 13:26     ` assistant.el " Reiner Steib
2007-12-11 16:22   ` emacs->gnus merge questions Ted Zlatanov
2007-12-17 23:02     ` Ted Zlatanov
2007-12-17 23:03       ` Ted Zlatanov
2007-12-18 20:25       ` Ted Zlatanov
2007-12-18 22:52         ` encrypt.el glue to PGG library added (was: emacs->gnus merge questions) Ted Zlatanov
2008-02-16 13:12       ` encrypt.el " Reiner Steib
2008-02-28 14:55         ` encrypt.el Ted Zlatanov
2008-02-28 20:28           ` encrypt.el Reiner Steib
2008-03-10 15:06             ` encrypt.el Ted Zlatanov

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=874petkgw8.fsf@catnip.gol.com \
    --to=miles@gnu.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).