From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [OT] git-annex: a new option for ConTeXt distribution (kickstarter campaign ends in 4 days)
Date: Fri, 8 Jun 2012 18:04:23 +0200 [thread overview]
Message-ID: <CALBOmsYg+C-tqagwqq4LPvE8rdJ1NgGDLWMqcNcKdP2gDGN-jA@mail.gmail.com> (raw)
In-Reply-To: <CALBOmsbt0_b3Jnv0fFWF41UDW2KK0pEbjm18TpFGT1L4ZWkNhg@mail.gmail.com>
> Actually, my original idea/suggestion was actually slightly different
> and would probably not need any additional software to be installed,
> but would not necessary be in scope of this project. I'm still looking
> for a way to have a "smarter" rsync server, so that I could use
> something like
> rsync -av rsync://contextgarden.net/suite/context/@tag:2013.12.13T12:13
> texmf-context/
> and rsync would then serve files from a particular branch/tag/sha of a
> git repository, without the need to have different version of
(I'm sorry for the incomplete paragraph.)
I wanted to say that this would allow switching to an arbitrary
version/date of distribution via rsync without having to provide all
those files as flat files on the server. Providing 700 unzipped
version of ConTeXt on the server is definitely not feasible, but the
.git repository of that only consumes 33 MB.
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
___________________________________________________________________________________
prev parent reply other threads:[~2012-06-08 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 16:00 Mojca Miklavec
2012-06-08 16:04 ` Mojca Miklavec [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=CALBOmsYg+C-tqagwqq4LPvE8rdJ1NgGDLWMqcNcKdP2gDGN-jA@mail.gmail.com \
--to=mojca.miklavec.lists@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).