##// END OF EJS Templates
config: pass both relative and absolute paths to `include` callback...
config: pass both relative and absolute paths to `include` callback The `include` callback is responsible for loading configs from `%include` statements. The callback currently gets passed the absolute path [1] to the config to read. That is created by joining the dirname of the file that contains the `%include` statement. For PyOxidizer support, I'm trying to reduce dependence on paths. This patch helps with that by passing the relative path found in the `%include` statement (but with username expansion, etc.) to the `include` callback. It also turns out that the existing callers can easily adapt to using the relative path. Coming patches will clean that up and then we'll remove the absolute path from the callback. [1] The "absolute path" bit is a bit of a lie -- it's going to be an absolute path if the path that was passed into `config.parse()` was absolute. Differential Revision: https://phab.mercurial-scm.org/D8790

File last commit:

r41072:ce0bc295 default
r45768:f7f142d7 default
Show More
TODO.rst
21 lines | 782 B | text/x-rst | RstLexer
Gregory Szorc
narrow: remove narrowrevlog...
r39807 Address commentary in manifest.excludedmanifestrevlog.add -
Augie Fackler
narrow: add a TODO document...
r36121 specifically we should improve the collaboration with core so that
add() never gets called on an excluded directory and we can improve
the stand-in to raise a ProgrammingError.
Reason more completely about rename-filtering logic in
narrowfilelog. There could be some surprises lurking there.
Martin von Zweigbergk
narrow: update TODO.rst now that we share format with sparse...
r40116 Formally document the narrowspec format. For bonus points, unify with the
server-specified narrowspec format.
Augie Fackler
narrow: add a TODO document...
r36121
narrowrepo.setnarrowpats() or narrowspec.save() need to make sure
they're holding the wlock.
Martin von Zweigbergk
narrow: move remaining narrow-limited dirstate walks to core...
r40123
The follinwg places do an unrestricted dirstate walk (including files outside the
narrowspec). Some of them should perhaps not do that.
* debugfileset
* perfwalk
* sparse (but restricted to sparse config)
* largefiles