RE: Re: Any way to apply a filename filter to compare revisions ( or show differences as unified diff)?

Yup. I'm just trying to improve visibility into what changes have been
committed. On larger projects oversight is critical, and being able to
filter the noise that doesn't apply is pretty important. I'm just
looking for a way to both ignore or include only files of a certain
type. Search for log of revisions gets me there partially for the
"include only" functionality (although the tortoise proc search leaves a
lot to be desired). Really some reg expression filter capability for the
compare revisions dialog would be best (as it quickly shows me the files
and what changes were made to the files clearly).

-----Original Message-----
From: Simon Large [mailto:simon@skirridsystems.co.uk]
Sent: Tuesday, February 27, 2007 1:41 PM
To: users@tortoisesvn.tigris.org
Subject: Re: Any way to apply a filename filter to compare revisions (
or show differences as unified diff)?

Peter McNab wrote:
> Simon Large wrote:
>> Peter McNab wrote:
>>> Simon Large wrote:
>>>>
>>>> Your first statement is correct, and the cumbersome workaround
>>>> wouldn't work at all. Ignore patterns only work for files which are

>>>> not yet versioned. Once you have placed a file under version
control
>>>> there is no way to ignore it.
>>> Sorry, I wasn't aware that the case if you svn deleted it from
>>> continued rev control?
>>
>> I was talking about the cumbersome workaround that Seth mentioned.
>> Naturally if you svn delete (and commit) items they become
unversioned
>> once more.
>>
>> Simon
>>
> Just confirmed my understanding, that once files are removed (svn
> deleted) from rev control then those files can be ignored.
> And the process is not that hard.
> Svn Delete them, Commit, Check for modifications, Tick show
unversioned
> files, right click each, Ignore them, (they disappear from list) and
> Commit.
> Bingo, you only see what you want to see. Oh, and untick show
> unversioned when done.
>
> So for .DCUs you only have to ignore one for them all to disappear
from
> the list.
>
> And if some files e.g. .CFG files are important to QA or whoever then
> they probably should be of interest to everybody so the know when
> something they just did changed the config.
>
> I'm just not comfortable with the idea I could locally hide a revision

> controlled file, make local changes and commit without knowing that in

> advance of the commit. That is the feature Seth is asking for.

I don't think Seth is asking for this in the commit dialog, just as a
filter for the review process, maybe in the log dialog.

Simon

-- 
        ___
   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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org