From: "mikael ciocca" <fung7955beaucham@tulsashometeam.com>
Cc: emacs-devel@gnu.org, emacs-bidi@gnu.org, emacs@gnu.org,
elton@gnu.org, elp-hurd-admin@gnu.org, emacs-commit@gnu.org,
eliz@gnu.org, elm@gnu.org
Subject: Re: 2nd Notice
Date: Fri, 18 Mar 2005 06:04:34 -0500 [thread overview]
Message-ID: <EKOI8478_IS_7584o@tulsashometeam.com> (raw)
[-- Attachment #1.1: Type: text/html, Size: 544 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
reply other threads:[~2005-03-18 11:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=EKOI8478_IS_7584o@tulsashometeam.com \
--to=fung7955beaucham@tulsashometeam.com \
--cc=eliz@gnu.org \
--cc=elm@gnu.org \
--cc=elp-hurd-admin@gnu.org \
--cc=elton@gnu.org \
--cc=emacs-bidi@gnu.org \
--cc=emacs-commit@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs@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).