Suggestion: Mixed-revision warning message in Log Messages dialog

[Stefan Hett]

Hi,

last week I've been reminded by a colleague reporting the problem to me about a scenario which I take it a lot of especially new users of TSVN have trouble with getting right.

Assume you bring up the TSVN log dialog of your project (in this case for TSVN 1.9):

The user (understandably) reads this as his checkout being up-to-date (since he's at the highest listed revision - aka: 1837042) and hence expects his WC being up-to-date.
However, this is not necessarily the case. There are several situations which can give the false impression here (f.e. you don't see here that subversion/po/de.po I actually updated to an older revision and hence that file even though part of the bold revision is not up to date at all!).

A common mishap which regularly happens to our users here is that one commits some changes while another person also commits something. Bringing up the revision of the person who committed the later change would also show the previous commit of the other user in the log, however (if the change was done in a different file/path) he would not actually have the corresponding changes in his WC.

I've got no real suggestion here for a perfect "fix"/"change"/"improvement" since I understand that any perfect solution would be quite performance demanding (also on the server). But maybe at least a red warning could be displayed at top of the window in case the log is displayed for a mixed-revision working copy to point out that part of the displayed changes might not be present yet?

Or does anybody have a better/different solution to that "problem" I might have not considered yet?

-- 
Regards,
Stefan Hett, Developer/Administrator

EGOSOFT GmbH, Heidestraße 4, 52146 Würselen, Germany
Tel: +49 2405 4239970, http://www.egosoft.com
Geschäftsführer: Bernd Lehahn, Handelsregister Aachen HRB 13473

Datenschutzhinweis:
Ihre personenbezogenen Daten, die Sie uns im Rahmen einer
Kontaktaufnahme zur Verfügung stellen, werden bei uns vertraulich
und entsprechend unserer Datenschutzerklärung behandelt:
http://www.egosoft.com/privacy_de.php
Privacy:
Any personal information you provide when contacting us will
be kept confidential and processed according to our privacy
policy: http://www.egosoft.com/privacy_en.php

[Stefan]

The problem with a warning label is that if it's there all the time, users tend to blend it out and as soon as the warning really applies to them, they won't even see it anymore.

[Stefan]

Certainly that's right, but I can't think of a better (i.e. feasible to
implement/add) alternative. That way at least users would have a chance
to spot the potential issue. W/o such warning they'd have little to no
hint about it.

But I can understand if you don't feel strongly about adding such
warning message there.

Regards,
Stefan