On Wed, Aug 05, 2009 at 03:14:11PM -0400, Steve Dickson wrote: > After thinking about this.. I've convinced myself that the internal > parsing routines should make the Section names case-insensitive > but the rest of the data (i.e the tag, value) should be returned as is > and let the callers deal with the case... > > The reason being everything hangs off Section names. So making those > easier to find I think is a good thing and hopefully it will make > managing config files a bit less error prone.... That's probably not what I would do, but I could live with that, as long as we're preserving the case of paths and user/group names. By the way, it looks like the git code to handle their extended section names (the [key "string"] thing) is in git's config.c:get_extended_base_var(), if that's a useful example. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
