From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: etc/MORE.STUFF
Date: Wed, 14 Jul 2004 14:27:23 -0400 [thread overview]
Message-ID: <E1BkoTT-0004HN-6b@fencepost.gnu.org> (raw)
In-Reply-To: <200407132338.i6DNcOD10530@raven.dms.auburn.edu> (message from Luc Teirlinck on Tue, 13 Jul 2004 18:38:24 -0500 (CDT))
Is etc/MORE.STUFF, accessible from the menu-bar under Help, "Find
Extra Packages", important enough to add updating it to
admin/FOR-RELEASE?
It would be nice to check MORE.STUFF, but given how hard
it will be to do the rest of what we need to do,
I'd rather not wait for that.
prev parent reply other threads:[~2004-07-14 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 23:38 etc/MORE.STUFF Luc Teirlinck
2004-07-14 8:43 ` etc/MORE.STUFF Kai Grossjohann
2004-07-14 18:27 ` Richard Stallman [this message]
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=E1BkoTT-0004HN-6b@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).