From: "John A. Martin" <jam@jamux.com>
Subject: Re: Please, we need a header back, soon!
Date: Thu, 09 Nov 2006 11:33:47 -0500 [thread overview]
Message-ID: <87lkmkwpec.fsf@athene.jamux.com> (raw)
In-Reply-To: <87wt64lhx0.fsf@magla.zg.iskon.hr>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
>>>>> "Zlatko" == Zlatko Calusic
>>>>> "Re: Please, we need a header back, soon!"
>>>>> Thu, 09 Nov 2006 17:10:51 +0100
Zlatko> Yes, it's too much philosophy for today. :) -- Zlatko
No philosophy needed. Instead please see
<ftp://ftp.rfc-editor.org/in-notes/rfc2919.txt> .
HTH
jam
[-- Attachment #2: Type: application/pgp-signature, Size: 154 bytes --]
next prev parent reply other threads:[~2006-11-09 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 15:10 Zlatko Calusic
2006-11-08 15:30 ` Nedko Arnaudov
2006-11-08 22:33 ` Katsumi Yamaoka
2006-11-09 7:18 ` Steinar Bang
2006-11-08 16:27 ` Reiner Steib
2006-11-09 15:44 ` Jason L Tibbitts III
2006-11-09 15:56 ` Zlatko Calusic
2006-11-09 16:00 ` Zlatko Calusic
2006-11-09 16:02 ` Jason L Tibbitts III
2006-11-09 16:10 ` Zlatko Calusic
2006-11-09 16:33 ` John A. Martin [this message]
2006-11-21 9:31 ` Didier Verna
2006-11-21 15:13 ` Jason L Tibbitts III
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=87lkmkwpec.fsf@athene.jamux.com \
--to=jam@jamux.com \
/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).