Skip to content
Snippets Groups Projects
Commit 45c18f7345c1 authored by Danny Hooper's avatar Danny Hooper
Browse files

narrow: consider empty commits to be "inside the narrow spec" for templates

It doesn't seem useful to exclude them, or harmful to include them. Users
writing log templates using outsidenarrow as a predicate might consider it
unexpected if their locally created empty drafts are treated as if they
contained something outside the clone.

Differential Revision: https://phab.mercurial-scm.org/D6414
parent 5b795108dd17
No related merge requests found
......@@ -37,7 +37,7 @@
repo = context.resource(mapping, 'repo')
ctx = context.resource(mapping, 'ctx')
m = repo.narrowmatch()
if not m.always():
if ctx.files() and not m.always():
if not any(m(f) for f in ctx.files()):
return 'outsidenarrow'
return ''
......
......@@ -281,6 +281,10 @@
marked working directory as branch foo
(branches are permanent and global, did you want a bookmark?)
$ hg ci -m empty
$ hg log -T "{rev}: {desc} {outsidenarrow}\n"
2: empty
1: add d5/f outsidenarrow
0: add d0/f outsidenarrow
$ hg pull -q
Can widen the empty clone
$ hg tracked --addinclude d0
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment