Mercurial > hg
comparison 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 |
comparison
equal
deleted
inserted
replaced
41147:eb172f9c208c | 41148:8eaf693b1409 |
---|---|
50 $ hg tracked | 50 $ hg tracked |
51 I path:inside/f | 51 I path:inside/f |
52 $ hg files | 52 $ hg files |
53 inside/f | 53 inside/f |
54 | 54 |
55 XXX: we should not have sparse enabled | 55 XXX: we should have a flag in `hg debugsparse` to list the sparse profile |
56 $ cat .hg/sparse | 56 $ test -f .hg/sparse |
57 [include] | 57 [1] |
58 inside/f | |
59 | 58 |
60 $ cat .hg/requires | 59 $ cat .hg/requires |
61 dotencode | 60 dotencode |
62 exp-sparse | |
63 fncache | 61 fncache |
64 generaldelta | 62 generaldelta |
65 narrowhg-experimental | 63 narrowhg-experimental |
66 revlogv1 | 64 revlogv1 |
67 sparserevlog | 65 sparserevlog |