From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Dev Context <dev-context@ntg.nl>,
ConTeXt list <context@lists.launchpad.net>
Subject: announcing server change, possible downtime
Date: Fri, 28 Oct 2011 15:16:17 +0200 [thread overview]
Message-ID: <CALBOmsbHY=BVzi7pAqG-4-gEbf6tSJWg_UCJi7FzsRiTPfnRKA@mail.gmail.com> (raw)
Dear ConTeXt-ers,
in the following days we will piecewise move parts of old server to a
new machine (this will happen once again, but this time it might be
slightly more dramatic change). Thus I would like to ask you to be
patient if something stops working.
The wiki has already been moved, so this should not be a problem. Some
sites will be reorganized, but I will inform you about details. In
particular, minimals will also change, but details will follow.
One thing that might be a tiny bit problematic are SVN repositories.
We need to upgrade them from SVN 1.5 to 1.7, so anyone using SVN
repositories from garden *might* need to do a fresh checkout. I didn't
test anything yet though, I only know that I had problems with the
client on my machine now that MacPorts upgraded SVN. (I have also
found a weird bug in 1.7.1 client.) I have no idea how server-side
upgrades behave on clients. This should more or less affect only me,
Taco and those who build binaries for minimals. Plus those who work on
meeting/group website occasionally.
Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
reply other threads:[~2011-10-28 13:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CALBOmsbHY=BVzi7pAqG-4-gEbf6tSJWg_UCJi7FzsRiTPfnRKA@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--cc=context@lists.launchpad.net \
--cc=dev-context@ntg.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).