"Simon Large" <simon@skirridsystems.co.uk>
wrote in message news:4533E629.3080706@skirridsystems.co.uk...
> Jeff Godfrey wrote:
> >
> > It just made sense to me that it should only report on the *filtered*
> > list I was currently looking at. So, as I change the filters at the
> > bottom, the reported revisions might change based on the currently
> > visible files.
> >
> > Either way, it's not overly important to me, though I think my
> > suggestion seems more "correct". Again, I could be totally wrong. If
> > that's the case, feel free to let me know.
>
> You still haven't answered the question "what would that information be
> good for?". How does knowing the last-updated revision of a subset of
> the files help you in any practical way? I'm not even sure how useful it
> is when applied to all files, except that it says your WC is not updated
> to the same revision.
>
Well, what is the current information good for? The change would mean that
the current information makes sense, rather than being a random snippet of
information about something different to what you are looking at.
If you can't justify the point of the current information then simply remove
it. If you can, then the same reason applies to the above, and should be
fixed as per the OP's suggestion.
Just my £0.02
- Mark Clements
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Oct 17 14:13:42 2006