Simon Large schrieb:
> On 15/10/2007, Hans-Werner Dietz <hans-werner.dietz@dbt.de> wrote:
>> I have a feature request. I like to see a different Icon if a version is
>> "mixed". I think best is a new icon, but also the "modified" Icon is
>> better than the green "normal" Icon because mixed versions are not
>> really clean.
>
> No, we will not add any more icons:
> http://tortoisesvn.net/node/3
I know this and expect that you are angry about new icons. But the users
has to be notified in some way. Maybe an Icon or something else. But a
green Icon, which most users understand as "ALL-OK" is definitely not
the best way for a possible mixed version.
>
>> The reason is that there are many developers who think that the green
>> "normal" Icon from TSVN means that their actual working copy is clean
>> and that they can very easily reproduce all green directories from the
... snip...
>> Status 3) A gets 1001 mixed (even if an "update" only pushes the "mixed"
>> away without getting updates in the source code at the working
>> copy)
>> Status 4) B gets 1002 mixed
>> Status 5) B gets 1002 (without mixed)
>>
>> At 3) and 4) SubWcrev gives me the information that I have to make an
>> Update. So in this case another Icon for the working copy's directory is
>> better to indicate the mixed-revision situation
>
> SubWCRev is not telling you that there is more information in the
> repository, only that your WC has not been updated to the same
> revision throughout. At stage 3, if user A updates he will get a
> normal, unmodified, unmixed working copy. After B commits his changes,
> SubWCRev will continue to give A the same result. It does not contact
> the repository.
>
I know that at stage 3 User A stays at his revision 1001 and is NOT
notified, that user B made a new revision. But that is exact what I
expect and what I DONT want to change. I know that SubWcRev gives the
same result and it is OK: If somebody checks out this revision for
debugging an old version of the program he exact gets the same sources
as the developer has on the working copy.
BUT: At stage 4 it is not so. If somebody later checks out revision 1002
he get state 5. So if the developer tests and delivers the version at
state 4 he has no easy optical notification that he does something
wrong. Of course it is the developers fault not to make an update after
commit. I know this and I handle it correct. But most people don't, they
only see green and assumes that everything is ok. And also if they
enable the SVN columns in the explorer: SVN Revision tells them Revision
1002 and no easy hint.
> The only reliable way to check is to use Check for Modifications and
> use the 'Check repository' button.
>
> Simon
>
I don't want to check the repository for Modifications online. If a made
a commit, than unplug the network cable and than call SubWcRev: It
correctly tolds me that the version number AND that the version is
possible mixed.
Hans-Werner
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Oct 15 14:29:00 2007