I have a vague answer; one of the full-time developers might be able to
elaborate.
On Tue, 2001-12-04 at 05:47, Sam.Cooper@scisys.co.uk wrote:
> I was wondering if svn could do a diff to a local repository which could be
> imported into the server repository. Basically, the German developers would like
> to be able to share their code locally using svn, we would like to be able to
> share our code locally using svn, and then once a week synch the changes. One of
> the two would be 'labelled' the master copy.
We may get most of this functionality eventually (it's one vision of how
distributed repositories might work), but most of it is post-1.0. You
might be able to play around with --xml-file options in the current
code, though.
> I have no idea what I would want svn to do to be able to support this set-up,
> hence the posting ;-).
What you really want is Bitkeeper. In the bitkeeper model (as I
understand it), every working directory is a repository. Repositories
are organized hierarchically; your external people could each have their
own working-dir/repository, and they could all feed into a central
external repository, which could in turn feed into the internal
repository. You can generate changesets and mail them upstream for the
external -> internal step.
Unfortunately, Bitkeeper is not a free software product in the sense
that Subversion is. You would have to purchase a commercial license for
Bitkeeper, since the freely available version insists (by code and by
license) that you log all changesets to openlogging.org--which is almost
certainly not acceptable for your military projects.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:51 2006