RE: GUI Diff on Repository HEAD and "a" directory?

The answer is that the statement: "Typical situation" is a context sensitive
statement... In SVN, "everyone checking out their own copy" is "Typical" In
visual source safe, strictly speaking it's not possible for everyone to
check out their own copy. VSS uses strictly "Locking" for version control.
One person at a time can officially have the file checked out. If more than
one person actually wants to work on the same file at the same time and at
least one person is going to check the file out, then everyone else has no
choice to do a "Get latest copy" (SVN equivalent of Export) to get a copy of
the file they can work on out of the REPO.

I don't want to get into a "which method is better" argument here... as I've
said, I find good and bad in both approaches... but this is the situation as
I see it.

-----Original Message-----
From: Les Mikesell [mailto:lesmikesell@gmail.com]
Sent: Monday, March 19, 2007 1:42 PM
To: Tom Malia
Cc: users@subversion.tigris.org
Subject: Re: GUI Diff on Repository HEAD and "a" directory?

Tom Malia wrote:

> So far, from my developing understanding of SVN, I think an analogous
> scenario in SVN would be something like:
>
> 1) Programmer 1 (the "lucky guy") checks out the entire project and starts
> developing in the same working directory he checked out to. This "lucky"
> guy can perform standard "diffs" against his base when we wants to see
> exactly what he has changed.
> 2) The others (the "unlucky guys") check out the entire code to a SVN
> working directory, then they export the exact same code to another
> directory. These guys do their development in the exported code and
perform
> Diff's against the "real" svn working directory when they want to see what
> changes they've made since they checked things out.

The question is, why do you think this is desirable compared to the
typical situation where everyone just checks out their own copies and
commits/updates frequently if they want to cooperate closely and take
advantage of each other's changes, or they make a branch if they want to
isolate changes that might be disruptive? Merging the changes on the
branch(es) would be the equivalent to your manual diff/merge step but
svn does most of the work for you.

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org