Potential BC changes to sparse before freeze

[Augie Fackler]

On Sat, Jul 15, 2017 at 03:15:08PM -0700, Sean Farley wrote:
>
> Gregory Szorc <gregory.szorc at gmail.com> writes:
>
> > On Sat, Jul 15, 2017 at 1:28 PM, Sean Farley <sean at farley.io> wrote:
> >
> >>
> >> Martin von Zweigbergk via Mercurial-devel <mercurial-devel at mercurial-
> >> scm.org> writes:
> >>
> > It's worth noting that sparse profiles today can contain "set:" entries to
> > yield the power of filesets (the matcher constructor automatically
> > recognizes the type of pattern). What we can't do is change how [include]
> > and [exclude] interact with each other.
>
> Perhaps this is specialized / nuanced enough that I don't quite follow;
> but that's fine. All I wanted to do is point out similar, existing
> behavior. If that's already been considered and deemed not suitable,
> then ok with me.

We tried using straight filesets for narrowhg's include/exclude logic,
and it was thornier than we'd have liked. So far being a little more
restrictive has simplified both server implementations *and* not
caused any end-user problems.