From: Marc van Dongen <dongen@cs.ucc.ie>
Cc: Mailing List <ntg-context@ntg.nl>
Subject: Re: LaTeX/ConTeXt/metapost repository
Date: Thu, 28 Dec 2000 15:32:24 +0000 [thread overview]
Message-ID: <20001228153224.Q17402@cs.ucc.ie> (raw)
In-Reply-To: <3.0.6.32.20001228015259.00929310@pop.wxs.nl>; from pragma@wxs.nl on Thu, Dec 28, 2000 at 01:52:59AM +0100
Hans Hagen (pragma@wxs.nl) wrote:
[snip]
: but ... the most important todo is probably the keyword part, which needs
: to be standardized pretty good
What I also would like to propose is that the thing is set-up
so that people can maintain their own contributions without
too much overhead. Hopefully, this will engourage people to
improve their solutions.
[snip]
[libraries, docs]
: wave for a nice and weird style. So, next year there will probably be
: contributions from our site.
I'll be looking forward to it.
Regards,
Marc
next prev parent reply other threads:[~2000-12-28 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 19:42 Marc van Dongen
2000-12-28 0:52 ` Hans Hagen
2000-12-28 15:32 ` Marc van Dongen [this message]
2000-12-28 21:50 ` Hans Hagen
2000-12-29 14:51 ` Marc van Dongen
2000-12-29 15:12 ` Hans Hagen
2000-12-29 15:40 ` Marc van Dongen
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=20001228153224.Q17402@cs.ucc.ie \
--to=dongen@cs.ucc.ie \
--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).