On Tue, Nov 6, 2012 at 1:49 PM, Paul Burba <ptbu...@gmail.com> wrote:
> If we ultimately decide[1] to allow svn:global-ignores to be > disregarded with the --no-ignore option, then I suggest it makes sense > for 'svn add' and 'svn import' to disregard the svn:auto-props > property when the --no-auto-props option is used. Anyone disagree? > > [1] And it certainly looks as if we are going in that direction. I'll > give this thread a day before making any changes, so all interested > parties have a chance to weigh in. On Wed, Nov 7, 2012 at 2:40 AM, Markus Schaber <m.scha...@codesys.com> wrote: > I'm neither a core developer, nor a sysadmin, but I tend to prefer > --no-ignore behaving the same for all 3 types of ignores, and using hooks > for "waterproof" blocking of files. On Wed, Nov 7, 2012 at 2:52 AM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Making 'svn add --no-auto-props' disregard svn:auto-props is > a bulletproof solution to the above. On Wed, Nov 7, 2012 at 4:39 AM, Branko Cibej <br...@wandisco.com> wrote: > Precisely. "ignored" has /never/ meant that you couldn't "svn add" a > file that matches the ignore pattern. Therefore, --no-ignores should > always ignore all ignores. I believe we have consensus at this point. So I'm going to make the requisite changes so that svn:global-ignores are disregarded with the --no-ignore option and svn:auto-props are disregarded when the --no-auto-props option is used. -- Paul T. Burba CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development Skype: ptburba
