From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: MH-E manual update
Date: Fri, 09 Dec 2005 20:50:01 +0200 [thread overview]
Message-ID: <uirtyjeau.fsf@gnu.org> (raw)
In-Reply-To: <9362.1134139251@olgas.newt.com> (message from Bill Wohler on Fri, 09 Dec 2005 06:40:51 -0800)
> cc: emacs-devel@gnu.org, mh-e-devel@lists.sourceforge.net
> Date: Fri, 09 Dec 2005 06:40:51 -0800
> From: Bill Wohler <wohler@newt.com>
>
> Would adding a mention of MH-E 8.0 source and manual be appropriate for
> the FOR-RELEASE file?
Yes, I think so. But please wait for Richard to give the definitive
answer.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-09 18:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 0:27 MH-E manual update Bill Wohler
2005-12-09 11:58 ` Eli Zaretskii
2005-12-09 14:40 ` Bill Wohler
2005-12-09 18:50 ` Eli Zaretskii [this message]
2005-12-09 21:15 ` Richard M. Stallman
2005-12-10 0:25 ` Bill Wohler
2005-12-10 16:18 ` Richard M. Stallman
2006-03-07 1:29 ` Bill Wohler
2006-03-11 14:30 ` Eli Zaretskii
2006-03-11 20:08 ` Bill Wohler
2006-03-11 21:35 ` Luc Teirlinck
2006-03-11 22:27 ` Bill Wohler
2006-03-11 23:08 ` Luc Teirlinck
2006-03-11 23:34 ` Bill Wohler
2006-03-11 23:24 ` Luc Teirlinck
2006-03-11 23:40 ` Bill Wohler
2006-03-11 23:39 ` Luc Teirlinck
2006-03-11 23:49 ` Bill Wohler
2006-03-12 2:39 ` Luc Teirlinck
2006-03-12 3:56 ` Bill Wohler
2006-03-12 0:39 ` Luc Teirlinck
2006-03-11 22:10 ` Eli Zaretskii
2006-03-11 23:32 ` Bill Wohler
2006-03-12 11:59 ` Robert J. Chassell
2006-03-13 12:55 ` Richard Stallman
2006-03-13 15:20 ` Robert J. Chassell
2006-03-13 16:29 ` Bill Wohler
2006-03-14 4:26 ` Eli Zaretskii
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=uirtyjeau.fsf@gnu.org \
--to=eliz@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).