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

Re: best recommended procedure?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-08-27 19:42:43 CEST

On Fri, 2004-08-27 at 12:39, Andres Paglayan wrote:
> Hi all,
>
> I have this situation,
>
> We are using an open source application which is publishing its
> Subversion repository on the internet through http, and they are
> committing changes every day. I don't have commit privileges over that
> tree.
> Ti fit our needs, I have many files tweaked and many others added to
> that project.
> Every time I download the latest version I need some -a lot of- time
> manually re-plugging my changes to that project.
>
> I have a Subversion installed in a Linux box and I use xp,
>
> My question is,
> Which would be the best way to create a branch from that project,
> considering that I can only read that repository?
>
> Would check out that repo and store it locally work? svn will not see
> remote changes on their server,
> Will then checking out that project daily work? svn will not keep
> track of the paired main/branch since the main is happening in a
> different servers.
>
> Can Subversion create a branch in my local server that is bonded to
> the trunk in theirs?
> if so, can someone point me in the right direction,
> if not, I will appreciate to hear any recommendation.

Subversion is a centralized system -- only one repository.

You sound like a perfect candidate for a decentralized system, where
everyone has private repositories. Try svk (http://svk.elixus.org),
which is a such a system, built on top of Subversion. You might also
want to look at the "Arch" vc system.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 27 19:44:42 2004

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