From: "Otared KAVIAN" <otared@gmail.com>
Subject: Re: i-Installer and ConTeXt updater
Date: Tue, 27 Jun 2006 23:39:30 +0200 [thread overview]
Message-ID: <3cb063a60606271439t55d1e55fh9c257095017cfb60@mail.gmail.com> (raw)
In-Reply-To: <f747c7a7c3d464a1e7bf4b89e7d9cb52@rna.nl>
On 6/27/06, Gerben Wierda <Gerben.Wierda@rna.nl> wrote:
> On Jun 27, 2006, at 21:59, Gerben Wierda wrote:
>
> > If Hans or Taco changes something, the i-Package is rebuilt and seeded
> > automatically every night (CET). Given that it is 8GB (with beta) and
> > it is uploaded to at least 4 repositories that takes some time (I have
> > a 1Mbps upload). But not hours.
>
> Ehh. 8MB of course ...
>
Hi Gerben,
Thanks to you for your answer and your efforts to maintain
i-Installer, and to Hans, taco and all other ConTeXters for their
wonderful work!
Indeed my message was not a complaint, just a feedback....
Best regards: OK
prev parent reply other threads:[~2006-06-27 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 16:04 Otared Kavian
2006-06-27 19:59 ` Gerben Wierda
2006-06-27 20:06 ` Gerben Wierda
2006-06-27 21:39 ` Otared KAVIAN [this message]
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=3cb063a60606271439t55d1e55fh9c257095017cfb60@mail.gmail.com \
--to=otared@gmail.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).