Date: Wed, 10 Aug 2011 23:31:12 -0500 From: Stephen Montgomery-Smith <stephen@missouri.edu> To: ctm-users@freebsd.org Subject: Re: SVN repo Message-ID: <4E435B10.9040907@missouri.edu> In-Reply-To: <CADLo839wy4VD0-fJ0jdHu-wnUgbdvCLTTpPdwEhhfKe841b-cA@mail.gmail.com> References: <CADLo839wy4VD0-fJ0jdHu-wnUgbdvCLTTpPdwEhhfKe841b-cA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/09/2011 07:49 AM, Chris Rees wrote: > Hi Stephen, > > Have you any plans to start distributing the subversion repo? I keep > hearing little hints about the Other Two Trees being moved too... If > you need any more hands on it I'll be happy to help. > > Chris OK, I think I have figured out how to do this, at least in principle. svn has all its data organized into revisions. These are numbered, starting at 1, and going on up to something like 224771. Every time someone commits to the svn repository, the revision number is incremented. There is the command: svnadmin dump whereever-the-repository-is \ -r 224703:224771 --incremental --deltas > afile so that if someone else has a repository going up to revision 224702, then they can update to revision 224771 with the command: svnadmin load whereever-the-other-one-is < afile. Furthermore, afile will just contain diffs needed to go from 224702 to 224771, and so it is not going to be larger than it needs to be. Obviously a wrapper can be written around these commands so that afile is sent out be email, and ctm and mkCTM can be written so that svn updates can be sent out by CTM. I'm still experimenting with this. And I don't think I will work seriously on this until the FreeBSD project gets close to abandoning cvs altogether. But I think that with some work, this can be made to work. Stephen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E435B10.9040907>