On Sun, Jul 17, 2016 at 10:15:55AM +0200, Johannes Schindelin wrote: > FWIW I am slightly less worried about the conditional includes (it is > already a horrible mess to figure out too-long include chains now, before > having conditional includes, for example). I am slightly more worried > about eventually needing to introduce support for something like > > [if-gitdir(...):section] > thisSettingIsConditional = ... > > or even > > [if (worktree==...):section] > anotherConditional = ... > > and then having two incompatible conditional constructs, one generic, the > other one specific to [include]. > > In other words, if we already introduce a conditional construct, I'd > rather have one that could easily be used for other conditions/sections > when (and if) needed.
I had assumed we would resist introducing anything like that, simply because of backwards compatibility issues with the syntax. But I admit that was just an assumption in my head; future compatibility with reality is not guaranteed. :) -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
