Show More
| @@ -1,23 +1,22 b'' | |||
|
|
1 | 1 | Integration with the share extension needs improvement. Right now |
|
|
2 | we've seen some odd bugs, and the way we modify the contents of the | |
|
|
3 | .hg/shared file is unfortunate. See wrappostshare() and unsharenarrowspec(). | |
|
|
2 | we've seen some odd bugs. | |
|
|
4 | 3 | |
|
|
5 | 4 | Resolve commentary on narrowrepo.wraprepo.narrowrepository.status |
|
|
6 | 5 | about the filtering of status being done at an awkward layer. This |
|
|
7 | 6 | came up the import to hgext, but nobody's got concrete improvement |
|
|
8 | 7 | ideas as of then. |
|
|
9 | 8 | |
|
|
10 | 9 | Address commentary in manifest.excludedmanifestrevlog.add - |
|
|
11 | 10 | specifically we should improve the collaboration with core so that |
|
|
12 | 11 | add() never gets called on an excluded directory and we can improve |
|
|
13 | 12 | the stand-in to raise a ProgrammingError. |
|
|
14 | 13 | |
|
|
15 | 14 | Reason more completely about rename-filtering logic in |
|
|
16 | 15 | narrowfilelog. There could be some surprises lurking there. |
|
|
17 | 16 | |
|
|
18 | 17 | Formally document the narrowspec format. Unify with sparse, if at all |
|
|
19 | 18 | possible. For bonus points, unify with the server-specified narrowspec |
|
|
20 | 19 | format. |
|
|
21 | 20 | |
|
|
22 | 21 | narrowrepo.setnarrowpats() or narrowspec.save() need to make sure |
|
|
23 | 22 | they're holding the wlock. |
General Comments 0
You need to be logged in to leave comments.
Login now