On Fri, Mar 21, 2008 at 10:36 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> "John M. Black" <johnmblack_at_gmail.com> writes:
> > [...]
>
> >
> > Please consider making Ignore pattern-matching case insensitive.
> >
> > OR at the very least, let the user choose. Maybe the easiest way to
> > do this is to keep the current Ignore property intact, and add a new
> > property "svn:ignoreNoCase". That way users can have it either way
> > for any item.
>
> How about a new property, "svn:Ignore", that means...
>
> Okay, sorry, bad joke.
>
> We could use an extra property, like you say, or a run-time
> configuration option, or both. The run-time option is probably easiest
> to implement. Would it be a compatibility break to have that option
> turned on by default (given that a user could always turn it off)? I
> don't know.
>
> Another possibility: be case-insensitive just for patterns of the form
> "*.foo", which probably covers more than 90% of the use cases.
>
> I'm just tossing out ideas here. At some point, we should take this
> thread to dev@, and see if we can get consensus on a solution. I do see
> your point about how the current behavior is (usually) not great.
>
> -Karl
>
How about adding configuration options to svn:ignore? Like .hgignore
does for setting the syntax.
eg.
--------------------------- .hgignore
# use glob syntax.
syntax: glob
*.elc
*.pyc
*~
.*.swp
# switch to regexp syntax.
syntax: regexp
^\.pc/
--------------------------- .hgignore
SVN could have an option:
option: [+-]casesensative
Where +casentative is the default option (and this maintains comapitility.
If this could potentially break current properties lists, there could
be another svn:ignore-options where these were set.
In the processes, couldn't '# blah...' be allowed as comments?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-22 19:11:16 CET