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

Re: traveling with subversion

From: Kyle Kline <kyle.kline_at_gmail.com>
Date: 2005-11-17 15:19:35 CET

I believe with SVK (or SVN for that matter), you should be able to share
patches with each other to keep each other up-to-date. SVK has good patch
management features.

On 11/17/05, Sean Moss-Pultz <sean@moss-pultz.com> wrote:
>
>
> On 2005/11/17, at $B>e8a(B 4:03, Karl Heinz Marbaise wrote:
>
> > Hi Sean,
> >
> >> My team is planning about a 2 to 3 week field test during which
> >> we will need to maintain a synced code base. Currently we are
> >> using subversion but we will not have access to this server on
> >> the road.
> >> I was thinking that It would be possible to mirror the repository
> >> using svk. While we are on the road all of us could use it's
> >> distributed repository features. Then when we return we could
> >> merge this back into our main subversion repository.
> >> Does anyone have any experience with something like this or
> >> another setup?
> > As you mentioned before SVK is the tool for the Job.
> > The other thing is you have to create a branch for every team
> > member on your repos.
> > Then every team member will mirror the particular branch for each
> > onto his local notebook (svk mirror http://svn.xxx.xx/project/
> > branches/member1 //project/member1/branch) after this each member
> > has to make a local branch where each one can work on (svk cp //
> > project/member1/branch //project/member1/local).
> > Now each member can checkout the source on its notebook (at this
> > point you can go abroad) and work on it and checkin changes localy
> > just using "svk ci".
> >
> > After you will be back to your companies network every member can do
> > and synchronizing the local changes into the repos using:
> > svk sm -I -l //project/member1/local //project/member1/branch
> > This will check in the changes you've made localy exaclty into your
> > repository (on the branches you've created before) incl. your log
> > messages.
> > Then you have all changes on the branches for every member on
> > companies server.
> >
> > Then just checkout a trunk copy and merge every branch after an
> > other in your trunk copy.
> >
> > That's it.
> >
> > Kind regards.
> > Karl Heinz
>
>
> Thanks a lot Karl. That seems to be exactly what we are looking for.
> Actually there would be one thing better. If when we were on the road
> our local repositories could also sync. Something very P2P ish. Does
> that exist? I read somewhere about SVL but I haven't been able to
> find anymore information.
>
> -Sean
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Received on Thu Nov 17 15:23:51 2005

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.