[PATCH 5 of 7] match: resolve 'set:' patterns first in _buildmatch()

Martin von Zweigbergk martinvonz at google.com
Thu Jul 5 14:42:05 EDT 2018


On Thu, Jul 5, 2018 at 7:15 AM Yuya Nishihara <yuya at tcha.org> wrote:

> # HG changeset patch
> # User Yuya Nishihara <yuya at tcha.org>
> # Date 1528613547 -32400
> #      Sun Jun 10 15:52:27 2018 +0900
> # Node ID c81f8e935af38b19a2004fb507bcf74783b0db06
> # Parent  eca5e10e8949810dc00b01bc84566393bba2bfae
> match: resolve 'set:' patterns first in _buildmatch()
>
> This just makes the next patch less complicated. The order of 'set:' and
> 'subinclude:' expansion doesn't matter.
>

How about if you subinclude a file that has a fileset in it? Is that not
possible because 'subinclude:' can only be used in .hgignore files and
'set:' cannot be used there? Or why does the order not matter?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20180705/aacfe371/attachment.html>


More information about the Mercurial-devel mailing list