From: Simon Josefsson <jas@extundo.com>
Subject: Re: ":version" entries in defcustoms
Date: Mon, 20 Sep 2004 00:29:45 +0200 [thread overview]
Message-ID: <iluisa9ki3q.fsf@latte.josefsson.org> (raw)
In-Reply-To: <v9wtyqf1jw.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> I don't know what to do with libraries as pgg*.el. Should we add
> `:version "21.4"' to all defcustoms there?
Is there a reason not to?
> Adding the custom version later (like I did) is annoying. How can we
> simplify this in the future? The problem is that we don't know the
> correct Emacs version number (which Emacs will contain this version of
> Gnus) to add when adding a variable in Gnus.
How about the approach of adding the proper :version cookies when the
files are integrated into Emacs? Then you know which version number
to use (i.e., the next one). If Gnus developers start to guess next
non-bugfix Emacs release numbers, things might be more difficult when
merging Gnus into Emacs in case the guess was wrong. If there is a
better way, then that's better, but I don't see it.
next prev parent reply other threads:[~2004-09-19 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 20:26 Reiner Steib
2004-09-19 22:29 ` Simon Josefsson [this message]
2004-09-19 23:02 ` Miles Bader
2004-09-20 16:39 ` Reiner Steib
2004-09-20 17:18 ` Simon Josefsson
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=iluisa9ki3q.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).