From: "Johannes Hüsing" <hannes@ruhrau.de>
Subject: Re: Marginal notes in two-column setup
Date: Thu, 24 Jul 2003 19:34:46 +0200 [thread overview]
Message-ID: <20030724173446.GB831@ruhrau.de> (raw)
In-Reply-To: <008501c3504c$d599aa20$0100a8c0@vademecum>
Willi Egger <w.egger@boede.nl> [Tue, Jul 22, 2003 at 02:27:58PM CEST]:
> Hi Gerben,
>
> Hm, was looking for the file at the pragma site. -- May be it was a
> preliminar release, which was then placed in a temporary directrory.
>
> I hop you will not find it excessive the file is 2.5MByte
>
One example why reply-to list by default is considered harmful.
http://www.unicom.com/pw/reply-to-harmful.html
--
Johannes Hüsing There is something fascinating about science. One gets
hannes@ruhrau.de such wholesale returns of conjecture from such a
trifling investment of fact. Mark Twain
prev parent reply other threads:[~2003-07-24 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 10:07 Gerben Wierda
2003-07-20 11:12 ` Willi Egger
2003-07-20 19:55 ` Gerben Wierda
2003-07-21 7:17 ` Willi Egger
2003-07-21 20:34 ` Gerben Wierda
[not found] ` <008501c3504c$d599aa20$0100a8c0@vademecum>
2003-07-24 6:36 ` Héctor M. Monacci
2003-07-24 17:34 ` Johannes Hüsing [this message]
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=20030724173446.GB831@ruhrau.de \
--to=hannes@ruhrau.de \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).