From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: emacs->gnus merge questions
Date: Sat, 08 Dec 2007 20:38:29 +0100 [thread overview]
Message-ID: <v94petj7t6.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <874petkgw8.fsf@catnip.gol.com>
On Sat, Dec 08 2007, Miles Bader wrote:
> 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
I'm not sure about this one. Ted?
> (2) deleted: assistant.el
Please don't delete assistant.el. I hope that someone will continue
developing it. (In Emacs, *.ast need to be removed as well.)
> (3) rename: password.el => password-cache.el
Yes, please do. Could you also sync the relevant changes from Emacs?
E.g. use...
(or (require 'password-cache nil t)
(require 'password))
> 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.
Yes, there is a discussion about this:
<http://thread.gmane.org/gmane.emacs.devel/84386/focus=65888>
I hope Richard won't object to keep the files the same in both CVSes
(e.g. imap.el) even if we add compatibility code like...
(eval-and-compile
(unless (fboundp 'declare-function) (defmacro declare-function (&rest r))))
BTW, sometimes it would be nice to know which changes have already be
synced from/to Emacs CVS and or compare.
What do you think about adding tags to Gnus CVS:
merge_to_emacs_trunk
merge_from_emacs_trunk
merge_to_emacs_22
merge_from_emacs_22
After you have done the merge, (re)tag the repositories.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-12-08 19:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 3:24 Miles Bader
2007-12-08 19:38 ` Reiner Steib [this message]
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=v94petj7t6.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).