[PATCH 09 of 13 sparse] merge: move sparse config parsing from sparse extension

[Martin von Zweigbergk]

On Jul 1, 2017 6:55 PM, "Gregory Szorc" <gregory.szorc at gmail.com> wrote:

# HG changeset patch
# User Gregory Szorc <gregory.szorc at gmail.com>
# Date 1498945185 25200
#      Sat Jul 01 14:39:45 2017 -0700
# Node ID a2d07300bdc999403954e965debf53db898ccdc3
# Parent  6636a2dfa31cb84684373bf3a9fdb03c26e42f99
merge: move sparse config parsing from sparse extension

This function is generic and doesn't need to be a repo method.

This patch also marks the beginning of moving code from sparse.py
into core. The goal is for the extension to enable the feature and
provide any UI adjustments.

merge.py may seem like a weird destination. But that's
where code for working directory updating lives. Unless we want
to create a new module for just the sparse bits or something for
working directory code, merge.py is the best current place.


It seems to me like there will be too much sparse-related code for it to
all move into merge.py. I think I'd prefer to move it into a
mercurial/sparse.py or something like that.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20170702/e3b7f305/attachment.html>