Re: Unversioned vs Ignored in Check for Modifications

On 09/10/2007, Stefan Küng <tortoisesvn@gmail.com> wrote:
> Josha Foust wrote:
> > In the Check for Modifications screen, I noticed a problem with the
> > definition of Unversioned vs Ignored. When both of those check boxes
> > are checked, files in subdirectories of Ignored directories show up as
> > Unversioned.
> >
> > Example:
> > A/
> > 1/
> > 2/
> > ab.txt
> > cd.txt
> >
> > If svn:ignore of "A" is "2" then "2" will show up as ignored, but
> > "ab.txt" and "cd.txt" will show up non-versioned. This seems incorrect
> > to me. Is this by design or accident?
>
> This is by design. the svn:ignore property can only ignore items
> directly below it. "ab.txt" and "cd.txt" are in an ignored subfolder,
> they're not ignored anymore by the svn:ignore property - so they're
> really unversioned.

That may be true, but it doesn't make a lot of sense from the user's
point of view, and it is not consistent with the CLI.

svn status -v --no-ignore

shows the ignored folder but not its children.

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