> > > > At this point I'd rather wait for Daniel to answer my question and
> > > > clarify his problem statement.
> > >
> > > I rather suspect that XX* and YY* were just general examples, not
> > > concrete ones.
> > So do I, but the solution I posted is generalizable, as you know.
> These were indeed just general examples. In practice there will be more
> than two patterns as well.
> I must admit I haven't experimented much with the glob pattern (admittedly,
> I suck at this!) but I have a feeling the complexity will increase rapidly
> when the number combinations (and variations) increase.
Yes, it will… but there might be room for, say, a tool that takes as
input a list of patterns and outputs the svn:ignore property value to
use. That won't be hard to write, and the main selling point would be
that it would work under existing releases as well.
> I think a separate property that is evaluated at the same time as
> svn:ignore is a lot easier to explain ("A file is ignored if the name
> satisfies one pattern in the svn:ignore list and satisfies NO pattern in
> the 'reverse of svn:ignore' property") than a convoluted regex.
No argument here. I never objected to an additional property, you
know; I just wanted to finish turning that last stone. See you on dev@ ☺
> The downside with a new property is that GUI implementors *may* want
> to implement additional support in the GUI for optimum user
I don't see how that's a downside.
Received on 2020-06-17 20:22:51 CEST