Mercurial > hg
diff tests/test-narrow-sparse.t @ 41148:8eaf693b1409
sparse: don't enable on clone if it was a narrow clone
When both sparse and narrow extensions are enabled and we do a narrow clone,
sparse enables itself because it reads --include flag and thinks that user is
trying to do a sparse clone.
This patch changes that behavior, and now if both extensions are enabled and
user passes `--narrow`, then the includes and excludes won't be considered as
part of sparse profile.
Differential Revision: https://phab.mercurial-scm.org/D5479
author | Pulkit Goyal <pulkit@yandex-team.ru> |
---|---|
date | Mon, 24 Dec 2018 15:30:39 +0300 |
parents | eb172f9c208c |
children | 76dcf7958c5f |
line wrap: on
line diff
--- a/tests/test-narrow-sparse.t Mon Dec 24 15:01:47 2018 +0300 +++ b/tests/test-narrow-sparse.t Mon Dec 24 15:30:39 2018 +0300 @@ -52,14 +52,12 @@ $ hg files inside/f -XXX: we should not have sparse enabled - $ cat .hg/sparse - [include] - inside/f +XXX: we should have a flag in `hg debugsparse` to list the sparse profile + $ test -f .hg/sparse + [1] $ cat .hg/requires dotencode - exp-sparse fncache generaldelta narrowhg-experimental