RE: Last commit revision will not update after commit

HI Stefan,

Thanks for very prompt answer...

I know it's TSVNCache, not svn cache.. And I understand it is by design
(that was even my first sentence). But I would still like to open this
question, because I think that more people could run into such problem. I
don’t want to change current behavior (I understand how and why it is
implemented this way), but I would like to see something like Last Local
Commit property that would identified that last revision to which anything
inside current folder was committed was X (or even better have array - so
you could programmatically say something like if there are any commitments
between Last Update and Last Local Commit, notify user that there are some
probably).

To give you idea, problem in our environment is that we gave GUI around
subversion... So users see local revision (based on folder) and last
deployed revision...
If they commit something from their package, root folder still reports last
update revision (which I understand). Problem is that when they compare,
they see old vs. old. So this is more question what to do when you want to
use something like me :(

Thanks for any ideas\recommendations,
Martin

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
Sent: Wednesday, May 21, 2008 11:01 AM
To: users_at_tortoisesvn.tigris.org
Cc: martin.zugec_at_gmail.com
Subject: Re: Last commit revision will not update after commit

Martin Zugec wrote:
> Hello Stefan,
>
> I understand this is by design, but isnt there any option to make
> mixture optional (some settings in preferences)? It would be really
> nice if one thread from svncache could update this in parent folders,
> right now it is very confusing for all my people - after commiting,
> they still see old revision under Last Commit :(

See here why this is not a good idea:
http://groups.google.com/group/Subversion-development/browse_thread/thread/b
8d0cafbe7c2650b/6e8825682ddc1c5d?#6e8825682ddc1c5d

Also, it's 'TSVNCache', not svncache. Which means the cache is part of TSVN,
not the core svn library. And that further means that it can not change any
Subversion metadata at all.

If your people find this concept too confusing, I would say that this is a
clear indication that they have not understood the concept yet (VSS
converts? It takes a long time to fix whatever VSS screwed up - not just in
a repository that got corrupted but also in its users minds).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org