Julian Foad wrote on Tue, Nov 06, 2012 at 15:29:33 +0000:
> ----- Original Message -----
> > From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
> > To: Paul Burba <ptburba_at_gmail.com>
> > Cc: dev_at_subversion.apache.org
> > Sent: Monday, 5 November 2012, 22:23
> > Subject: Re: disregarding svn:global-ignores
> >
> > Paul Burba wrote on Mon, Nov 05, 2012 at 21:45:23 -0500:
> >> On Mon, Nov 5, 2012 at 5:41 PM, Daniel Shahaf
> > <d.s_at_daniel.shahaf.name> wrote:
> >> >
> > http://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps#Ignores_.22Hierarchy.22
> >> > says 'svn status --no-ignore' does not disregard inherited
> >> > 'svn:global-ignores' properties.
> >>
> >> Hi Daniel,
> >>
> >> Sorry, that section is out of date, I corrected it. The --no-ignores
> >> option still works for status, it's only for import and add that it
> >> can't be overridden.
> >>
> >
> > Perfect, thanks. I think not-overriding for add/import is fine: for
> > 'import' only the repository files are affected, and for 'add'
> > files
> > matching the pattern can be specified explicitly in the argv targets
> > (and auto-props added can be modified or stripped after 'add' and before
> > 'commit').
>
> Am I the only one going "Eww!" on reading this?
>
> We have three ways of specifying ignores, and we have an option that disregards them, only in one cammand it disregards all of the ways and in two other commands the option only disregards two of the ways. And we say "sure, that sounds perfect". It doesn't sound fine to me, it sounds horrible.
>
> What am I missing?
>
Do 'add' and 'import' already take the '--no-ignore' flag? My answer
was assuming they didn't.
Also Julian you might want to review the semantics of svn:auto-props?
According to the wiki page there is no way to override or ignore those
upon add/import, either - I'm not completely happy with that.
> - Julian
>
>
> >
> >> > This breaks a use-case for me:
> >> > % svn status --no-ignore | xargs rm -rf
> >> >
> >> > How, with a 1.8 client, would I obtain a complete list of all
> >> > unversioned files in my working copy? "Complete" means -
> > without
> >> > excluding any files (regardless of inherited props, runtime config,
> > etc)
> >>
> >> Here's my trunk WC (with no global-ignores set in my config):
> >>
> >> Note that the unversioned *.py files are revealed with the --no-ignore
> > option:
> >>
> >> trunk_at_1406029>svn st --depth immediates --no-ignore
> >> M .
> >> I merge_annotate_log_bug.py
> >>
> >
> > Thanks for the detailed answer.
> >
> > Cheers
> >
> > Daniel
> >
> >> --
> >> Paul T. Burba
> >> CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
> >> Skype: ptburba
> >
Received on 2012-11-06 19:25:21 CET