Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Gnus 5.11 in Emacs CVS
Date: Wed, 14 Jan 2004 06:15:36 +0100	[thread overview]
Message-ID: <m3u12z9klj.fsf@defun.localdomain> (raw)
In-Reply-To: <v94quza3q9.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Tue, 13 Jan 2004 23:22:22 +0100")

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

> Some minor problems (see the comments about "load-path shadows" in the
> script):
>
> # Not needed for GNU Emacs (XEmacs compatibility library)
>   $rm gnus/gnus-xmas.el{,c}

Also messagexmas.el, nnheaderxm.el, dgnushack.el gnus-load.el and
lpath.el.

> # Gnus can use the file from net/ instead:
>   $rm gnus/netrc.el{,c}

I think netrc.el is primarily maintained in Gnus, so the Gnus version
should be used.

> # The version from calendar/ lacks `time-to-number-of-days'
>   $rm calendar/time-date.el{,c}

Ditto.

> manuals="emacs-mime.texi gnus-faq.texi gnus.texi message.texi
>          pgg.texi sieve.texi"

We should remove the @iflatex stuff from gnus.texi

    sed -e '/@iflatex/,/@end iflatex/d' $< >

otherwise you can't use the normal procedure to tex it.

Other stuff to consider:

* The refcard.  emacs/etc already has refcards for dired, viper
  etc. so we might as well include it.

* The ChangeLogs.

* Fix some of the numerous byte-compiler warnings you get when you
  compile Gnus as a part of Emacs [1].

* Maybe some other files from Gnus should go to net/, e.g. dig.el,
  dns.el ... -- I don't know.

[1] In some ways I think we're doing ourselves a disservice with the
    elaborate compilation scheme.  With cvs Emacs (at least) most of
    it should be unnecessary because `(if (fboundp' kills the
    warnings.




  parent reply	other threads:[~2004-01-14  5:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 11:01 Per Abrahamsen
2004-01-05 21:18 ` Steve Youngs
2004-01-05 22:01   ` Reiner Steib
2004-01-06  5:08     ` Lars Magne Ingebrigtsen
2004-01-08 17:58       ` Reiner Steib
2004-01-13 22:22         ` Reiner Steib
2004-01-13 23:08           ` Jesper Harder
2004-01-14  5:15           ` Jesper Harder [this message]
2004-01-14  6:20             ` Simon Josefsson
2004-01-15  0:46               ` Jesper Harder
2004-01-15  2:30                 ` Simon Josefsson
2004-01-14 14:18             ` Reiner Steib
2004-01-22  7:43           ` Jesper Harder
2004-01-22 15:17             ` Reiner Steib
2004-02-15  0:03               ` Miles Bader
2004-02-15  0:18                 ` Miles Bader
2004-04-14 20:24                 ` Reiner Steib
2004-04-15  0:37                   ` Miles Bader
2004-05-12 10:17                     ` Reiner Steib
2004-01-05 22:12   ` Xavier Maillard
2004-01-06 13:46   ` Per Abrahamsen

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=m3u12z9klj.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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).