From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Strange requirement...
Date: Mon, 24 Jul 2006 17:50:01 -0400 [thread overview]
Message-ID: <E1G58JN-0005fq-4L@fencepost.gnu.org> (raw)
In-Reply-To: <85slkrpk6k.fsf@lola.goethe.zz> (message from David Kastrup on Mon, 24 Jul 2006 08:54:11 +0200)
This gives, however, no clue about how to deal with declaring versions
of an external package that is _not_ distributed as part of Emacs
(notably AUCTeX).
You just follow the instructions for :package-version.
They seem clear to me. If you don't find them clear,
could you explain why?
next prev parent reply other threads:[~2006-07-24 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 6:54 Strange requirement David Kastrup
2006-07-24 21:50 ` Richard Stallman [this message]
2006-07-25 7:29 ` David Kastrup
2006-07-25 22:15 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1G58JN-0005fq-4L@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).