This is an archive of the discontinued Mercurial Phabricator instance.

Differential D4902

narrow: update TODO.rst now that the narrowspec is in .hg/store
ClosedPublic

Authored by martinvonz on Oct 5 2018, 7:07 PM.

Details

Reviewers
durin42
pulkit
Group Reviewers
hg-reviewers
Commits
rHG937ce75ea18c: narrow: update TODO.rst now that the narrowspec is in .hg/store
Summary

We no longer have the unfortunate wrappostshare() and
unsharenarrowspec() since 576eef1ab43d (narrow: move .hg/narrowspec to
.hg/store/narrowspec (BC), 2018-08-02).

Diff Detail

Repository
rHG Mercurial
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

martinvonz created this revision.Oct 5 2018, 7:07 PM
pulkit accepted this revision.Oct 5 2018, 7:16 PM
Closed by commit rHG937ce75ea18c: narrow: update TODO.rst now that the narrowspec is in .hg/store (authored by martinvonz). · Explain WhyOct 5 2018, 7:17 PM
This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

PathPackages
Mhgext/narrow/TODO.rst (3 lines)

Diff 11730

hgext/narrow/TODO.rst

Integration with the share extension needs improvement. Right now Integration with the share extension needs improvement. Right now
we've seen some odd bugs, and the way we modify the contents of the we've seen some odd bugs.
.hg/shared file is unfortunate. See wrappostshare() and unsharenarrowspec().
Resolve commentary on narrowrepo.wraprepo.narrowrepository.status Resolve commentary on narrowrepo.wraprepo.narrowrepository.status
about the filtering of status being done at an awkward layer. This about the filtering of status being done at an awkward layer. This
came up the import to hgext, but nobody's got concrete improvement came up the import to hgext, but nobody's got concrete improvement
ideas as of then. ideas as of then.
Address commentary in manifest.excludedmanifestrevlog.add - Address commentary in manifest.excludedmanifestrevlog.add -
specifically we should improve the collaboration with core so that specifically we should improve the collaboration with core so that