From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: ack.texi
Date: Thu, 18 Dec 2008 01:52:14 -0500 [thread overview]
Message-ID: <e63agmc6w1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <b1prjq2hb3.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 18 Dec 2008 00:17:20 -0500")
Glenn Morris wrote:
> Come to think of, is ack.texi really necessary, given that etc/AUTHORS
> exists? AFAICS, the former is just a less complete, harder to update
> version of the latter.
Rambling away to myself, I suppose ack.texi is a bit more readable
than AUTHORS.
next prev parent reply other threads:[~2008-12-18 6:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 2:57 ack.texi Glenn Morris
2008-12-18 5:17 ` ack.texi Glenn Morris
2008-12-18 6:52 ` Glenn Morris [this message]
2008-12-18 19:48 ` ack.texi Eli Zaretskii
2008-12-19 1:27 ` ack.texi Glenn Morris
2008-12-19 7:42 ` ack.texi Eli Zaretskii
2008-12-20 18:03 ` ack.texi Richard M Stallman
2008-12-19 7:33 ` ack.texi Richard M 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=e63agmc6w1.fsf@fencepost.gnu.org \
--to=rgm@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).