Brush John (KCPA 11) wrote:
> Since we have to wait around 30s for the log messages to show, this is a fairly critical problem. Otherwise, an excellent tool!
Caching log messages would be very neat.
Definitely doable, since repository revisions is immutable..
Well, except that log messages can be changed if you add a hook that allows it.
We could happily ignore that fact and tell users to turn off caching
if they do that and vice versa. Perhaps a radio button that allows
two selections, "enable log message/author editing" and "cache log
messages"...
We'd probably need a unique identifier (GUID sort of) that identifies
each repository, so we can detect when a repo is changed on the server
(pulled away and replaced by another or what not)?
Or maybe just some silly workaround, like having the messages in
cache, but retrieving messages from HEAD and back to the latest
revision in the cache - including the latest revision in the cache.
Do a compare and say things are OK if that top entry from the cache
matches the first (oldest) of the entries just retrieved.
A log message cache would remove the need for the "Get all messages"
buttons too, thus simplifying the GUI.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Mar 30 15:58:13 2005