[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "Check for Modification" dialog - possible enhancement?

From: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2006-10-16 22:06:01 CEST

Jeff Godfrey wrote:
> ----- Original Message ----- From: "Stefan Küng" <tortoisesvn@gmail.com>
>> Actually, it shows the lowest/highest revision of the whole working
>> copy tree below the one you selected to bring up the dialog.
>> What would that information be good for?
>> I don't like the idea of showing different information there without
>> knowing why.
> Stefan,
> Thanks for the quick answer. I'll try to explain my reasoning, though
> as a fairly SVN / TSVN User, I could be just plain wrong. If that's the
> case, please accept my apologies. Here's how I typically use the "Check
> for modifications" dialog...
> - I have a checked-out folder containing hundreds of source files, of
> which I may have modified say, 4.
> - I right-click on the *folder* itself, and select "Check for modification"
> - Again, by default, I have the modifications dialog setup so that
> *none* of the options are checked at the bottom.
> This gives me a good overview of the (versioned) files in the folder
> that I've modified (4 files in the above example).
> Now, the reason for the request...
> I'm looking at a dialog that contains the 4 modified files. The actual
> revisions of those 4 visible files range from "11-13", but at the bottom
> of the dialog I see the ranges listed as "2-13". At first, I was
> confused by the "2-13" report, then I realized that it was actually
> reporting on all the version controlled files in the selected directory
> (at least that's what I decided) - even though I wasn't currently
> *looking* at all of those files.
> 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.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Oct 16 22:05:39 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.