From: Taco Hoekwater <taco@elvenkind.com>
Cc: ntg-context@ntg.nl
Subject: Re: Re[4]: Indexing
Date: Fri, 22 Feb 2002 17:35:31 +0100 [thread overview]
Message-ID: <20020222173531.19484c4d.taco@elvenkind.com> (raw)
In-Reply-To: <1088548016.20020222143741@bigfoot.com>
Ok, I'll setup a framework for approval bij Hans.
Expect more in a couple of days ...
On Fri, 22 Feb 2002 14:37:41 +0100
"Giuseppe Bilotta" <bourbaki@bigfoot.com> wrote:
>
> Friday, February 22, 2002 Taco Hoekwater wrote:
>
> TH> You're back at it, aren't you? :-)
>
> Of course I am! I think it's *extremely* important!
>
> --
> Giuseppe "Oblomov" Bilotta
--
groeten,
Taco
next prev parent reply other threads:[~2002-02-22 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 17:24 Indexing John Culleton
2002-02-21 9:33 ` Indexing Taco Hoekwater
2002-02-22 0:22 ` Indexing John Culleton
2002-02-22 9:41 ` Indexing Taco Hoekwater
2002-02-22 11:38 ` Re[2]: Indexing Giuseppe Bilotta
2002-02-22 12:25 ` Taco Hoekwater
2002-02-22 13:37 ` Re[4]: Indexing Giuseppe Bilotta
2002-02-22 16:35 ` Taco Hoekwater [this message]
2002-02-25 14:00 ` Indexing Hans Hagen
2002-02-25 21:12 ` Indexing John Culleton
2002-02-26 10:01 ` Indexing Taco Hoekwater
2002-02-26 11:14 ` Indexing Hans Hagen
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=20020222173531.19484c4d.taco@elvenkind.com \
--to=taco@elvenkind.com \
--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).