From: Miles Bader <miles.bader@necel.com>
Cc: eliz@gnu.org, emacs-devel@gnu.org, nickrob@snap.net.nz, storm@cua.dk
Subject: Re: (emacs)Antinews
Date: Thu, 26 Jan 2006 10:39:47 +0900 [thread overview]
Message-ID: <buoslrbrcm4.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <200601252338.k0PNcEO19568@raven.dms.auburn.edu> (Luc Teirlinck's message of "Wed, 25 Jan 2006 17:38:14 -0600 (CST)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Its primary purpose is to provide accurate and useful
> info about differences with earlier Emacs versions.
Have you ever actually read the antinews?
-miles
--
"I distrust a research person who is always obviously busy on a task."
--Robert Frosch, VP, GM Research
next prev parent reply other threads:[~2006-01-26 1:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 0:09 (emacs)Antinews Luc Teirlinck
2006-01-25 1:08 ` (emacs)Antinews Nick Roberts
2006-01-25 2:19 ` (emacs)Antinews Luc Teirlinck
2006-01-25 2:53 ` (emacs)Antinews Nick Roberts
2006-01-25 3:44 ` (emacs)Antinews Luc Teirlinck
2006-01-25 4:36 ` (emacs)Antinews Eli Zaretskii
2006-01-25 8:54 ` (emacs)Antinews Kim F. Storm
2006-01-25 17:52 ` (emacs)Antinews Eli Zaretskii
2006-01-25 19:47 ` (emacs)Antinews Andreas Schwab
2006-01-25 23:38 ` (emacs)Antinews Luc Teirlinck
2006-01-25 23:58 ` (emacs)Antinews Andreas Schwab
2006-01-26 0:14 ` (emacs)Antinews Luc Teirlinck
2006-01-26 4:31 ` (emacs)Antinews Eli Zaretskii
2006-01-26 1:39 ` Miles Bader [this message]
2006-01-26 4:30 ` (emacs)Antinews Eli Zaretskii
2006-01-26 5:13 ` (emacs)Antinews Chong Yidong
2006-01-27 22:32 ` (emacs)Antinews Richard M. Stallman
2006-01-26 17:46 ` (emacs)Antinews Richard M. Stallman
2006-01-26 2:47 ` (emacs)Antinews Richard M. Stallman
2006-01-25 15:45 ` (emacs)Antinews Richard M. Stallman
2006-01-25 2:27 ` (emacs)Antinews Luc Teirlinck
2006-01-25 2:55 ` (emacs)Antinews Nick Roberts
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=buoslrbrcm4.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=nickrob@snap.net.nz \
--cc=storm@cua.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.