Justin Erenkrantz wrote:
> On 5/21/07, C. Michael Pilato <firstname.lastname@example.org> wrote:
>> That's true, but to what degree do we care? We've only ever
>> publicized our
>> option names in lower-case form -- in samples, documentation, and
>> discussion. So why would somebody choose to use a different form?
>> because they tried it and nothing fell completely over (for them)?
>> Shame on
> Silently ignoring config options because the case is wrong seems bad, IMO.
> I think it'd be better to normalize filenames before checking the
> autoprops code. This would mean that we lose case-sensitivity on the
> applicability of the autoprops, but I view that as a far lesser evil.
> -- justin
Yeah, I think I have to agree. For one thing, it's easy to document that
our autoprop application is done case-insensitively. But secondly, folks
might actually *prefer* this most of the time, even, especially if their
repositories are prone to winding up with upper-cased filenames thanks to
some Windows software.
C. Michael Pilato <email@example.com>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Mon May 21 18:24:46 2007