RE: Newbie Question

[Gavin Lambert <ga...@compacsort.com>]

Quoth Ernest L. Williams Jr. <ma...@ornl.gov>:
> No.  There are other collaborative ways in which works
> happens. We have some development servers in which we may put
> a project in a place that's shared by multiple developers.
> Developer 1 goes home and requests that Developer 2 update
> the project.

In which case instead of switching back and forth between developer
logins, you could create a shared login for the server.  That'd probably
be perfect if you only want the server's working copy to update, never
commit (since you can then enforce that by restricting the account to
read-only).

It's probably less than ideal if you want to commit from the server as
well (since you lose the info on which developer did the committing),
but depending on your other procedures this may not be a deal-breaker.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Newbie Question

["Ernest L. Williams Jr." <er...@ornl.gov>]

On Fri, 2006-09-01 at 12:15 +1200, Gavin Lambert wrote:
> Quoth Ernest L. Williams Jr. <ma...@ornl.gov>:
> > No.  There are other collaborative ways in which works
> > happens. We have some development servers in which we may put
> > a project in a place that's shared by multiple developers.
> > Developer 1 goes home and requests that Developer 2 update
> > the project.
> 
> In which case instead of switching back and forth between developer
> logins, you could create a shared login for the server.  That'd probably
> be perfect if you only want the server's working copy to update, never
> commit (since you can then enforce that by restricting the account to
> read-only).
> 
> It's probably less than ideal if you want to commit from the server as
> well (since you lose the info on which developer did the committing),
> but depending on your other procedures this may not be a deal-breaker.
> 


Again, we would like to work as we did in the CVS world.  Except that we
want to take advantage of all the nice features of SVN.

Once again, SVN_SSH is the answer for us.


Thanks,
Ernesto

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org