Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-mime-en@m17n.org
Subject: Re: Sync of Gnus with Emacs
Date: Fri, 03 Sep 2004 16:37:31 +0900	[thread overview]
Message-ID: <b9yacw74xc4.fsf@jpl.org> (raw)
In-Reply-To: <iluisaydow4.fsf@latte.josefsson.org>

>>>>> In <iluisaydow4.fsf@latte.josefsson.org> Simon Josefsson wrote:

> If somebody is syncing this with Emacs CVS, I think sha1-el.el should
> be renamed to sha1.el, and the callers updated.  The old name doesn't
> make sense now that sha1.el isn't around.  (The story used to be that
> sha1.el was a generic front end to sha1-el.el and sha1-dl.el, the
> latter which used dynamically loaded Emacs modules.)

There are still sha1.el, sha1-el.el and sha1-dl.el in FLIM.  But
now that's ok even if a user accidentally loads sha1.elc of FLIM.
I've made changes in sha1-dl.el yesterday so that it can be used
with Gnus.  I think people using the dynamically loaded module
are rare, though.

Please note, the released FLIM version can't be used with Gnus
because of the old sha1 modules.  So, I recommend those who use
FLIM for the particular purpose upgrade it to the CVS version.
The snapshot which I made unofficially is there:

http://www.jpl.org/ftp/pub/m17n/flim-1_14-************.tar.gz
 or ftp://ftp.jpl.org/pub/m17n/flim-1_14-************.tar.gz

(Where `************' is a timestamp which will vary.)

XEmacs users had better also use the latest ecrypto package or
Sumo.

Another solution is to rearrange the order of load-path.  Those
packages are apt to be preceded than Gnus by default.



  parent reply	other threads:[~2004-09-03  7:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 22:20 Reiner Steib
2004-08-22 22:33 ` Simon Josefsson
2004-08-23  8:33   ` Reiner Steib
2004-08-23  8:59     ` Simon Josefsson
2004-08-23 16:04 ` Ted Zlatanov
2004-08-24 15:49   ` Reiner Steib
2004-08-25  0:32     ` Katsumi Yamaoka
2004-08-25  8:35       ` Reiner Steib
2004-08-25  9:26         ` Katsumi Yamaoka
2004-08-26 10:00           ` Katsumi Yamaoka
2004-09-09 23:38       ` Miles Bader
2004-09-10  0:15         ` Katsumi Yamaoka
2004-08-31 15:58     ` Reiner Steib
2004-09-01 14:50     ` Simon Josefsson
2004-09-01 16:04       ` Reiner Steib
2004-09-01 20:20         ` Simon Josefsson
2004-09-01 23:03         ` Miles Bader
2004-09-03  7:37       ` Katsumi Yamaoka [this message]
2004-09-07 19:38     ` Ted Zlatanov
2004-09-08 18:20       ` Reiner Steib
2004-09-10 17:59         ` Ted Zlatanov
2004-09-11 15:08           ` Reiner Steib
2004-10-19  3:58     ` Kevin Greiner

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=b9yacw74xc4.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=emacs-mime-en@m17n.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).