Date: Sat, 26 Jan 2013 07:50:18 +1100 From: Peter Jeremy <peter@rulingia.com> To: Arrigo Marchiori <ardovm@yahoo.it> Cc: freebsd-stable@freebsd.org Subject: Re: Svnsup architecture [was: Re: svn - but smaller?] Message-ID: <20130125205018.GB29105@server.rulingia.com> In-Reply-To: <20130125124219.GA5299@snail.casa> References: <20130123144050.GG51786@e-Gitt.NET> <20130124093846.5e683474@laptop> <E10EBB96DCC143BE8F14FD2982AD84B7@white> <20130124085717.GA26673@icarus.home.lan> <20130125124219.GA5299@snail.casa>
next in thread | previous in thread | raw e-mail | index | archive | help
--Yylu36WmvOXNoKYn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2013-Jan-25 13:42:19 +0100, Arrigo Marchiori <ardovm@yahoo.it> wrote: >The current svnsup design is composed of: > > 1- svnsup-distill: takes a revision from svn and creates a text file > (called a delta) that represents it. It seems to be almost > complete. > > 2- svnsup-apply: takes a delta generated by svnsup-distill and applies > it to an existing source tree. It's currently a work in progress. > > 3- a server-side application that runs svnsup-distill and distributes > the deltas (still to be developed). > > 4- a client-side application that fetches new deltas and runs > svnsup-apply. New trees are "bootstrapped" from other sources, > e.g. weekly tarballs (still to be developed). I think you've just re-invented CTM. Before spending too much more time on svnsup, I suggest you read ctm(1). --=20 Peter Jeremy --Yylu36WmvOXNoKYn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEC8AoACgkQ/opHv/APuIeKZgCglaJi/4dhqA4gZ4CiBezu9W/2 +tEAnjVz5ZZJU2UL4Q47wcUvMhg7I16i =w0/s -----END PGP SIGNATURE----- --Yylu36WmvOXNoKYn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130125205018.GB29105>