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

Re: Newbie Question

From: Ernest L. Williams Jr. <ernesto_at_ornl.gov>
Date: 2006-09-01 00:59:55 CEST

On Fri, 2006-09-01 at 00:43 +0200, Ryan Schmidt wrote:
> On Sep 1, 2006, at 00:29, Ernest L. Williams Jr. wrote:
> > On Thu, 2006-08-31 at 12:05 -0500, Andrew Melo wrote:
> >
> >> Ernest L. Williams Jr. wrote:
> >>
> >>> That also does not work:
> >>>
> >>> [williams@ics-srv-phy1 svn-xaldev]$ svn switch --relocate svn
> >>> +ssh://tap@ics-srv01/sns/ADE/svnTop/svnroot/xaldev/trunk svn
> >>> +ssh://tap@ics-srv01/sns/ADE/svnTop/svnroot/xaldev/trunk
> >>> tap@ics-srv01's password:
> >>
> >> You will want to replace 'tap@ics-srv01' in the second trunk with
> >> your
> >> own username. the ssh layer is trying to use 'tap' as the
> >> username, if
> >> you replace it with yours, you should get access.
> >
> > Thanks for your help. Finally it works. :)
> >
> > Are you not surprised that SVN has two commands to perform this
> > operation where as CVS only required one?
> Which two commands?
svn --relocate
svn update

> Which operation?
I just want to do a svn update on an already checked out working copy.
The problem is that another user checkout the working copy.

> > I am trying to get used to the complexity of SVN when it comes to a
> > multi-user collaborative project. CVS has many disadvantages but
> > command syntax, execution, and basic administration seemed easier.
> > Although, I have been using CVS for a long time so my bias is showing.
> I still haven't understood why you're having to do this at all. Why
> are you reusing someone else's working copy? Everybody should have
> their own working copy in which they do their work.
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.

Sometimes developers work in their own sandbox as well.

Once, we have a RELEASE then things work differently.

Well, anyway that was how we did things sometimes in CVS and a simple
cvs -d $CVSROOT is what most people turned into an alias.

Nevertheless, one of the SVN users showed me how to use SVN_SSH and now
we are in business.

Thanks for everyone's help. :)


> The svn command syntax was modeled on the cvs command syntax, with
> the notable exception of the way branches and tags are handled. Is
> there anything in particular you're having difficulty with? I haven't
> used CVS but many here have and should be able to help you make the
> transition. There's also a section "Subversion for CVS users" in the
> book which you should probably read if you haven't already. It's at
> http://svnbook.org/

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 1 01:01:46 2006

This is an archived mail posted to the Subversion Users mailing list.