I don't think there's a solution to this 'cos eventually, something'll have to
merge the archive files. For example:
user-1 copies repo into repo-copy-1
user-2 copies repo into repo-copy-2
user-1 commits file onto repo-copy-1
user-2 commits file onto repo-copy-2
What happens when it's time to put the changes back into the original repo? I
suppose if everyone's working off of branches, the archive merges won't be too
bad. My guess is that only the branch numbers would have to be changed within
the merged archive. I don't see why this wouldn't be doable, but I don't know
if anyone's actually done this.
Noel
[EMAIL PROTECTED] on 03/06/2000 06:35:12 PM
To: [EMAIL PROTECTED]
cc:
Subject: Re: remote shared repositories
With client/server, I need to be able to talk to the remote
repository.
In my case, I might be on the net only late evenings (one phone
line), and still want to 'commit early, commit often'.
I am very strongly of the 'commit your changes frequently'
family (at least once per syntax error free make, or once at the
end of each work day, or once per major code re-organization);
with CVS, this means (or at least, seems to me to mean) commit
onto branches until the code is stable enough for others to see.
I can't do that if I can't talk to the remote.
I can run a local repository, but then I have two repositories
to synchronize.
Michael
Noel L Yap wrote:
>
> Why not just use client/server CVS?
>
> Noel
>
> [EMAIL PROTECTED] on 03/06/2000 03:52:17 PM
>
> To: [EMAIL PROTECTED]
> cc: (bcc: Noel L Yap)
> Subject: remote shared repositories
>
> How can I share a repository across two different machines?
>
> Lets say that two machines will talk to each other only once a
> night. Lets say that each machine has developers, and they want
> to work on a shared CVS project.
>
> How/can/is it possible for them to share/synchronize their CVS
> repositories? What limits do they get regarding who can be
> working on a given branch/how are different branches/trunks
> shared?
>
> Michael
