From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: Posting large modes in gnu.emacs.sources
Date: Sat, 01 Nov 2003 17:10:01 +0200 [thread overview]
Message-ID: <9003-Sat01Nov2003171001+0200-eliz@elta.co.il> (raw)
In-Reply-To: <jwv3cdajtep.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca> (message from Stefan Monnier on Thu, 30 Oct 2003 21:44:03 GMT)
> Newsgroups: gnu.emacs.help
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Thu, 30 Oct 2003 21:44:03 GMT
>
> It's really not that large. But note that many newsservers simply ignore
> large messages, so I recommend you post a URL instead.
> Other people disagree and think the full source is better because it then
> gets archived as part of gnu.emacs.source archive, so if you post a URL,
> make sure that the location will "live for ever".
So perhaps it's a good idea to do both for such large amounts of code.
next prev parent reply other threads:[~2003-11-01 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 20:57 Posting large modes in gnu.emacs.sources Arjan Bos
2003-10-30 21:44 ` Stefan Monnier
2003-11-01 15:10 ` Eli Zaretskii [this message]
2003-11-02 18:27 ` Arjan Bos
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=9003-Sat01Nov2003171001+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
/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).