Thanks for the reply. But To clarify: These are auto-generated versioned
files that I wish to ignore when looking at differences between two
revisions. As project lead I need to see real developer revisions when
comparing two build tags. For oversight, I currently use Compare
Revisions (or unified diffs) between two tags straight through the repo
browser. This gives me a quick look at actual modifications checked in
by all developers. However, the versioned build process generated files
(all with the same name) clog up the returned list of modified files :(
.
As far as I understand, the ignore patterns in global ignore or the
working folder ignore wouldn't give me this ability to filter out the
versioned files. There would seem be a pretty cumbersome workaround to
update a working folder to revision B, then add the ignore pattern, then
compare the working folder with revision A. Preferably, I'd like an
option that doesn't require a working folder at all (aka by comparing
actual repository revisions).
-----Original Message-----
From: Peter McNab [mailto:mcnab_p@melbpc.org.au]
Sent: Friday, February 23, 2007 3:52 PM
To: users@tortoisesvn.tigris.org
Subject: Re: Any way to apply a filename filter to compare revisions (
or show differences as unified diff)?
Gray, Seth wrote:
>
> Hi - I'm stuck with a code base that has a particular set of
> inconsequential files that are modified with almost every build. When
> I need to review differences for the project I need to be able to
> ignore these files. The results of a comparison in repo browser
> between revisions might have 4 or 5 files I'm concerned with, while
> containing 80 or so files I don't care about. Is there any way through
> Tortoise to apply a filename ignore pattern for revision
> comparison/diff generation?
>
This is an oft asked question that is well covered in the help.
Just search for "ignore" and follow the steps.
--The steps I use may help with the process--
Firstly "Update" your WC from the root folder so you can commit any
upcoming deletes and ignores.
Then SVN delete all (but only) the auto-generated files from your WC and
commit.
Commit the deletions.
Re-compile or build or whatever the process is that creates the
inconsequential files.
At the WC root folder right click SVN Check for Modifications.
At the bottom left of the Check for Modifications dialog tick just the
"Show unversioned files" checkbox.
Then starting at the top, one by one, left click on the file you want to
ignore.
Right Click on "Add to ignore list"
Choose whether this is to be by file-name or global by file type.
For global selections you will notice any other files of that type
present in the Check for Modifications dialog also disappear, showing
success at adding the ignore property.
Repeat for each other file type you don't wish to see.
Commit the changes.
Peter
---------------------------------------------------------------------
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
Received on Mon Feb 26 01:07:43 2007