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

Re: svn commit: rev 4988 - in trunk: . notes

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2003-02-21 03:25:12 CET

William Uther <willu@cse.unsw.edu.au> writes:
> You mean that introducing students to it was a bad idea? :)

No :-). It depends on the students.

> I have a team of 8 undergrads using svn for their honours project (US
> people - think senior thesis). Here is the current list of things
> I've noticed introducing them to subversion as their first revision
> control system:
>
> i) It is much easier to teach branching in subversion than CVS.
> ii) Branching is only somewhat useful at the moment as merging is
> poor. In particular, the software they are developing has been
> undergoing major code re-arrangements (the current group of undergrads
> inherited it from the previous group, and the handover process seems
> to involve lots of renaming... sigh). This breaks merging. Alot of
> the merging has been done manually.

It seems like we could use their bug reports, then.

> iii) The students take a while to pick up on the concept of a
> working copy and .svn directories. They like to copy bits of working
> copy around between users/machines. This doesn't work well... :)

Is it worse than CVS in this respect? Is there some way they can copy
bits of working copy around in CVS that they can't in Subversion?

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 21 03:58:47 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.