[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: need help for a specific usage...

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-12-01 20:29:15 CET

kfogel@newton.ch.collab.net wrote on 12/01/2004 02:16:25 PM:

> "madmax" <madmax@libertysurf.fr> writes:
> > I'm a team manager of an projet which consist in an implementation
> > of a module in a big opensource projet. The problem is that we want to
> > have a svn server for our developements of this module, staying
> > updated with the svn server of the original projet. The best would be
> > an access to the "branches" directory of their server, but we can't.
> > So the solution would be a mirror of their server in our server
> > (so that we could make updates) and here create a "branch" version,
> > containing the modifications. But I can't find a way to do this...
> >
> > So now I just import the files of all the opensource projet, and add
> > them to my svn repository. But here I lost all information on history
> > / updates...
> >
> > I supposed that I could merge files from 2 differents svn
> > servers... be svn refuse it.
> >
> > If you have a better solution, i'll be very happy.
> I have to wonder why you're not just doing your development in the
> open source repository...
> However, leaving aside that larger question, you want to use the
> methods described for "Vendor Branches" in
> http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-7-sect-4
> The description there is unfortunately known to have a minor bug or
> two, and there's an open ticket to get the documentation cleaned up,
> it just hasn't been done yet. I think you'll want to use the
> svn_load_dirs.pl method recommended there, be sure to read that
> script's own documentation.

I did not see the original message, so I am replying to Karl's reply.

We had a similar need. We are working on a port of Subversion to an
EBCDIC platform, so we wanted a branch of the Subversion repository to
work with as well as stay up to date. I solved the problem using svk. I
use svk to maintain a local mirror of the Subversion repository, I then
just make my own branches within that repository for my work. I can use
svk to keep the Subversion line up to date, and I can use svn merge and
whatever else, to keep my branch up to date.

In my case, I am only using svk to mirror the Subversion repository. Our
repository is then served up to developers via HTTP, and they are just
using TortoiseSVN or the command line to do normal Subversion-type work.

It works very well.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 1 21:54:43 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.