From: "Eckhart Guthöhrlein" <eckhart.guthoehrlein@uni-bielefeld.de>
Subject: Re: table questions
Date: Wed, 27 Apr 2005 14:15:21 +0200 [thread overview]
Message-ID: <20050427121521.GE6221@cebitec.uni-bielefeld.de> (raw)
In-Reply-To: <4268B420.3010608@wxs.nl>
On Fri, 22 Apr 2005 at 10:21:52+0200, Hans Hagen wrote:
> I'm fighting deadlines right now, but later i'll try to get a look at the
> current table thread (maybe someone can summarize the problem)
As discussed, I will remind you in a fortnight or so and sum up what is
missing about natural tables. Probably, there will be even more points
until then.
Greetings,
--
Eckhart
next prev parent reply other threads:[~2005-04-27 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 8:21 Hans Hagen
2005-04-27 12:15 ` Eckhart Guthöhrlein [this message]
2006-08-15 23:58 wwl
[not found] <mailman.357.1155686115.2039.ntg-context@ntg.nl>
2006-08-17 20:26 ` wwl
2006-08-17 22:08 ` Hans Hagen
[not found] <mailman.392.1155890252.2039.ntg-context@ntg.nl>
2006-08-18 15:09 ` wwl
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=20050427121521.GE6221@cebitec.uni-bielefeld.de \
--to=eckhart.guthoehrlein@uni-bielefeld.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).