On Wed, Jun 8, 2011 at 6:23 AM, Randolph, Christian [USA]
wrote:
> "Actually, I don't think we know that. The security based refusal to allow
> electronic communications between the systems will hamper *any* multi-homed
> development effort. We need to find out the extent of that restriction to
"Actually, I don't think we know that. The security based refusal to allow
electronic communications between the systems will hamper *any* multi-homed
development effort. We need to find out the extent of that restriction to give
good advice."
The restrictions are due to government classificati
Am Dienstag, den 07.06.2011, 08:13 -0500 schrieb Les Mikesell:
> Yes, I have a hard time visualizing how any tool can help with
> concurrent changes if one side doesn't stop while the merges happen
> both ways and the results get back.
Just look at Clearcase (again, sorry :) ). First, it has exce
On 6/7/11 6:52 AM, Nico Kadel-Garcia wrote:
On Mon, Jun 6, 2011 at 6:16 AM, Stefan Sperling wrote:
On Mon, Jun 06, 2011 at 11:55:42AM +0200, Andreas Tscharner wrote:
People here will hate me for this, but I think you should switch to a
DVCS (Distributed Version Control System), like Mercurial
On Mon, Jun 6, 2011 at 6:16 AM, Stefan Sperling wrote:
> On Mon, Jun 06, 2011 at 11:55:42AM +0200, Andreas Tscharner wrote:
>> People here will hate me for this, but I think you should switch to a
>> DVCS (Distributed Version Control System), like Mercurial or git.
>
> If people hate you for makin
Am Montag, den 06.06.2011, 07:52 -0500 schrieb Les Mikesell:
> If you are doing this in 2 directions, won't the disconnected
> repositories eventually drift out of sync as the people resolving
> conflicts make different choices - regardless of how well the VCS
> manages the details?
I guess you'r
On 6/5/11 10:58 PM, Nico Kadel-Garcia wrote:
On Sun, Jun 5, 2011 at 10:19 PM, Les Mikesell wrote:
If it doesn't take too long for a round-trip, you could ship the working
copy from site B to site A, do the commit and update, and ship it back
before doing any more work at site B.
Les, I'm loo
On 6/6/11 7:33 AM, Heinrichs, Dirk wrote:
Am Montag, den 06.06.2011, 11:55 +0200 schrieb Andreas Tscharner:
I am looking for suggestions from the community as to how
best address the setup issue outlined below.
We have two sites wanting to use Subversion that are
performing parallel development
Am Montag, den 06.06.2011, 11:55 +0200 schrieb Andreas Tscharner:
> > I am looking for suggestions from the community as to how
> > best address the setup issue outlined below.
> >
> > We have two sites wanting to use Subversion that are
> > performing parallel development of the same software. Du
On Sun, 05 Jun 2011 14:57:22 +, Randolph, Christian [USA] wrote:
...
> Is there a way to setup the two subversion repositories to somehow automate
> keeping the two repositories in sync?
No (AFAIF, as usual), not out of the box.
> We are usually passing media back and forth once a week, but
On Sun, 05 Jun 2011 20:52:38 +, Nico Kadel-Garcia wrote:
...
> If they can't communicate electronically, you'll have to synchronize
> by physical media. Subversion is built on top of CVS paradighms, with
> a central repository. Parall, disconnected development *cannot work*
> with that model,
On Mon, Jun 06, 2011 at 11:55:42AM +0200, Andreas Tscharner wrote:
> People here will hate me for this, but I think you should switch to a
> DVCS (Distributed Version Control System), like Mercurial or git.
If people hate you for making this suggestion then that's their fault.
Not every tool is ma
> I am looking for suggestions from the community as to how
> best address the setup issue outlined below.
>
> We have two sites wanting to use Subversion that are
> performing parallel development of the same software. Due to
> security restrictions, the two sites are unable to
> communicate elec
least
friendly with the courier.
Richard
- Original Message -
From: Nico Kadel-Garcia
Sent: 06/06/11 01:58 PM
To: Les Mikesell
Subject: Re: Two-Site Subversion Repository Setup Ideas
On Sun, Jun 5, 2011 at 10:19 PM, Les Mikesell wrote: >
If it doesn't take too long for a ro
On Sun, Jun 5, 2011 at 10:19 PM, Les Mikesell wrote:
> If it doesn't take too long for a round-trip, you could ship the working
> copy from site B to site A, do the commit and update, and ship it back
> before doing any more work at site B.
Les, I'm looking right at his original post.
> We have
On 6/5/11 7:52 PM, Nico Kadel-Garcia wrote:
On Sun, Jun 5, 2011 at 10:57 AM, Randolph, Christian [USA]
wrote:
I am looking for suggestions from the community as to how best address the
setup issue outlined below.
We have two sites wanting to use Subversion that are performing parallel
devel
On Sun, Jun 5, 2011 at 10:57 AM, Randolph, Christian [USA]
wrote:
> I am looking for suggestions from the community as to how best address the
> setup issue outlined below.
>
> We have two sites wanting to use Subversion that are performing parallel
> development of the same software. Due to se
Stefan Sperling wrote on Sun, Jun 05, 2011 at 17:33:56 +0200:
> Subversion has not been designed for server-independent operation.
> For proper operation you need either one central server or at least
> a mirror server that can contact the master over a network connection.
Or, alternatively, a mas
On Sun, Jun 05, 2011 at 02:57:22PM +, Randolph, Christian [USA] wrote:
> I am looking for suggestions from the community as to how best address the
> setup issue outlined below.
>
> We have two sites wanting to use Subversion that are performing parallel
> development of the same software.
I'm intrigued as to how people would answer this. Obviously, if you're only
going to sync the repos once per week, you're going to be fundamentally limited
by that.
Is your solution to use patchfiles? It should be pretty straightforward.
svn diff -rxxx:HEAD > patchfile
where xxx is the revi
20 matches
Mail list logo
