From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /n/sources/contrib/
Date: Sun, 18 Nov 2007 10:17:39 -0500 [thread overview]
Message-ID: <20071118151745.AF4DE1E8C4D@holo.morphisms.net> (raw)
In-Reply-To: <f9001ad47b12f73ba4f88ef005a055bc@proxima.alt.za>
> I started to mirror the entirety of /n/sources/contrib, but the
> results are disappointing.
>
> If I'm not mistaken, there is no "replica" facility around "contrib",
> could it be arranged?
The web page Uriel pointed at contains a recipe but no explanation.
The explanation is that every night the file /n/sources/lsr is updated
with a list of all the files on sources and their modification times,
sizes, and content hashes. You can copy lsr and then diff it against
your previous copy of lsr to find out which files have changed
and need to be updated in your "replica".
It's very easy. Much easier than trying to build something like this
on top of venti or fossil, and with the added benefit that you can
selectively mirror, excluding some trees as desired.
Russ
next prev parent reply other threads:[~2007-11-18 15:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 5:35 lucio
2007-11-17 18:05 ` andrey mirtchovski
2007-11-17 18:55 ` lucio
2007-11-17 18:56 ` lucio
2007-11-17 22:00 ` erik quanstrom
2007-11-18 4:39 ` lucio
2007-11-18 5:08 ` erik quanstrom
2007-11-18 5:30 ` lucio
2007-11-18 10:25 ` johnny
2007-11-18 11:04 ` lucio
2007-11-18 11:33 ` roger peppe
2007-11-18 13:24 ` lucio
2007-11-18 14:18 ` erik quanstrom
2007-11-18 18:17 ` johnny
2007-11-19 16:29 ` roger peppe
2007-11-18 21:23 ` johnny
2007-11-17 18:13 ` Uriel
2007-11-17 18:58 ` lucio
2007-11-18 15:17 ` Russ Cox [this message]
2007-11-18 15:29 ` erik quanstrom
2007-11-18 18:26 ` Francisco J Ballesteros
2007-11-19 2:15 ` Russ Cox
2007-11-19 17:38 ` erik quanstrom
2007-11-19 17:53 ` Russ Cox
2014-05-23 7:20 David Hoskin
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=20071118151745.AF4DE1E8C4D@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).