From: Hans van der Meer <hansm@science.uva.nl>
Subject: Re: error in patterns treatment?
Date: Sat, 28 Jan 2006 16:56:54 +0100 [thread overview]
Message-ID: <3858986B-30F9-4055-B411-9B16D3476616@science.uva.nl> (raw)
In-Reply-To: <43DB5535.3020209@elvenkind.com>
On Jan 28, 2006, at 12:27, Taco Hoekwater wrote:
> Hans van der Meer wrote:
>> Has something in the system changed?
>
> The Januari 27 version, or the one Hans uploaded this morning?
The 27 januari version. Downloaded it this morning, about 10.15 or so.
I guess from your question there is a new one and see it now on the
pragma site.
Will download it and see if problem gone.
I probably should have woken up somewhat later this morning :-)
yours sincerely,
dr. H. van der Meer
next prev parent reply other threads:[~2006-01-28 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 10:21 Hans van der Meer
2006-01-28 11:27 ` Taco Hoekwater
2006-01-28 15:56 ` Hans van der Meer [this message]
2006-01-29 16:52 ` Taco Hoekwater
2006-01-29 18:24 ` Hans van der Meer
2006-01-30 8:36 ` 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=3858986B-30F9-4055-B411-9B16D3476616@science.uva.nl \
--to=hansm@science.uva.nl \
--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).