Every one works in a team environment, if many people working in the same project is what you mean.
And I think by now you should know that, Show Change means diff with pristine copy, it means show what you have changed and it makes perfect sense.
Compare with revision means, compare the local file with svn server.
and new release will also have Compare with Head ( I have been waiting for this for a while)
Now which one should be default is what you argue.
btw, on a side note, from your mail, you seem to be maintaining a project (forgive me if i am wrong).
I have done maintenance in the past & in a team environment. No 2 engineers worked on the same problem at any given time. Engineers working on the branch were distributed over so many contries. From Japan, China, India Australia, UK, US working on the same trunk. But still no 2 engineers ever fixed the same problem.
Maybe you need to fix the process too :)
-prakash
________________________________
From: Andrew Scott <
ascott@...>
To: "
smartsvn@..." <
smartsvn@...>
Sent: Thursday, June 25, 2009 10:08:13 PM
Subject: RE: [smartsvn] Digest Number 1183
In a team environment if a member of my team changes the file I am working on, I then will have a conflict. Now I would need to show the changes or compare my working copy with SVN to see if the changes in that file impact on what I am working on.
And then make the necessary decision on what is needed to be merged, in either direction.
Especially if those changes then make my code redundant I need to see at a quick snap whether I am wasting my time fixing something that, could have been completely changed or even fixed by another developer.
From: smartsvn@yahoogroup s.com [mailto:smartsvn@yahoogroup s.com] On Behalf Of Jason Hughes
Sent: Friday, 26 June 2009 2:59 PM
To: smartsvn@yahoogroup s.com
Subject: Re: [smartsvn] Digest Number 1183
Andrew makes some good points about having server-related operations on
a separate menu from local-related operations. Perforce does a good job
of collecting Client, Task, Changelist, etc operations into separate
menus. This is handy, even if it makes some of the menus longer.
However, I have never found any reason to check my changes against the
HEAD. As long as there's a standard diff vs. local, and a diff vs.
revision/HEAD, I'm satisfied. If you want to add a smart diff that
checks local, then remote, then specific revisions, fine... but make
that a completely different command, because it would infuriate me to
see other people's changes when I'm trying to decide what my check-in
comment should be, and whether I want to check in a file at all.
I can't remember if SmartSVN comes this way or if I configured it, I
have double-click mapped to Diff. It's way faster than using a context
menu, and is generally the most-used operation (for me at least).
JH
--
Jason Hughes
President
Steel Penny Games, Inc.
Austin, TX
__._,_._
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/smartsvn/<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/smartsvn/join (Yahoo! ID required)
<*> To change settings via email:
mailto:
smartsvn-digest@...
mailto:
smartsvn-fullfeatured@...
<*> To unsubscribe from this group, send an email to:
smartsvn-unsubscribe@...
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/