From: storm@cua.dk (Kim F. Storm)
Cc: help-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs w32 FAQ links updation
Date: Thu, 12 Jan 2006 16:56:34 +0100 [thread overview]
Message-ID: <m37j95jv7x.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <20060112094358.69037.qmail@web52709.mail.yahoo.com> (Ramprasad B.'s message of "Thu, 12 Jan 2006 01:43:58 -0800 (PST)")
Ramprasad B <ramprasad_i82@yahoo.com> writes:
> Hi all,
>
> I have attached a "gnu_faq_links.zip" file which contains the links which are
> outdated.
Hi Ramprasad,
Please, on this list, always just include the actual text (or diff or
backtrace or whatever) rather than attaching zip files or other messy
stuff that we need to decode to read.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-01-12 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 9:43 Emacs w32 FAQ links updation Ramprasad B
2006-01-12 15:56 ` Kim F. Storm [this message]
2006-01-13 3:30 ` Ramprasad B
-- strict thread matches above, loose matches on Subject: below --
2006-01-12 14:02 Ramprasad B
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=m37j95jv7x.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-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.
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).