Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
From: "Cooke, Mark" <mark.cooke@siemens.com>
To: "users@subversion.apache.org" <users@subversion.apache.org>
CC: "Robert J. Gebis" <rjgebis@gmail.com>
Date: Wed, 26 Oct 2011 08:46:16 +0100
Subject: RE: Local svn proxy
Thread-Topic: Local svn proxy
Thread-Index: AcyTcmWHOt0QHjSGQomzqLK6u2cPFAAQHdHg
Message-ID: 
 <4F7A7621A511B945915EB16D655311D807A52D9E43@GBOXFW99E01MSX.ww005.siemens.net>
References: <9F6B5707-BD88-4A70-9035-B3CEA8B93D2D@gmail.com>
 <CALb=wn=mxy2fW6HmVuA3SVRXx-WdzWgvjkXX-v4tM=Mt9DMo=A@mail.gmail.com>
In-Reply-To: 
 <CALb=wn=mxy2fW6HmVuA3SVRXx-WdzWgvjkXX-v4tM=Mt9DMo=A@mail.gmail.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> > On Tue, Oct 25, 2011 at 17:35, Robert J. Gebis=20
> > <rjgebis@gmail.com> wrote:
> > I was wondering if there is a way to setup local svn proxy=20
> > so my commits could be committed locally before pushing them=20
> > to remote server. I am on Mac Book Pro and I am running=20
> > multiple virtual box with different os to develop/build and=20
> > test. Right now I have to commit changes from one platform=20
> > which could be breaking something on other.
> > Preferred way to handle this would be to have svn proxy of=20
> > some kind to to keep changes between local uses before=20
> > pushing them to remote server where other can get it in=20
> > building state (at least :)
>=20
> -----Original Message-----
> From: Andy Levy [mailto:andy.levy@gmail.com]=20
> Sent: 26 October 2011 01:00
> To: Robert J. Gebis
> Cc: users@subversion.apache.org
> Subject: Re: Local svn proxy
>=20
> Subversion supports a write *through* proxy, wherein you have a local
> mirror of the "master" repository and commits are relayed up to the
> master instead of being written to the proxy. But those commits aren't
> "staged" locally - they go immediately to the master.
>=20
> What it sounds like you really want a DVCS like git or Mercurial, or
> at least the git-svn bridge.
>=20
Is this not the sort of thing a branch is for?  Work on the server proper i=
n your own branch and then merge to "trunk" once complete...
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.html

Otherwise, there is a commercial solution that builds on subversion to allo=
w commits to a local server but that would replicate the changes to all oth=
ers which is not what I think you want.

~ mark c