upstream/mercurial-mirror Files · hgext/narrow/TODO.rst

fastannotate: process files as they arrive...

fastannotate: process files as they arrive peer.commandexecutor()'s context manager waits for all responses to arrive in its __exit__() method. We want to process the results as they arrive, so we should do that inside the context manager scope. Note that the futures' result() methods have been replaced to make sure that the command executor's sendcommands() method is called when the first future's result is requested, so we don't need to do that. A minor side-effect is that we can no longer easily tell when the server has started sending us responses, so that long statement was lost. Differential Revision: https://phab.mercurial-scm.org/D4666

Gregory Szorc - - Load All Authors

File last commit:

r39581:10a8472f default


                r39751:d8a7690c

default

Download file

             TODO.rst
        
                    30 lines
            
             | 1.3 KiB
            
                | text/x-rst
            
             |
                RstLexer
            
             / hgext / narrow / TODO.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        Augie Fackler
    
narrow: add a TODO document...

              r36121
            
      Integration with the share extension needs improvement. Right now

      we've seen some odd bugs, and the way we modify the contents of the

      .hg/shared file is unfortunate. See wrappostshare() and unsharenarrowspec().

      Resolve commentary on narrowrepo.wraprepo.narrowrepository.status

      about the filtering of status being done at an awkward layer. This

      came up the import to hgext, but nobody's got concrete improvement

      ideas as of then.

      Fold most (or preferably all) of narrowrevlog.py into core.

      Address commentary in narrowrevlog.excludedmanifestrevlog.add -

      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.

      Figure out how to correctly produce narrowmanifestrevlog and

      narrowfilelog instances instead of monkeypatching regular revlogs at

      runtime to our subclass. Even better, merge the narrowing logic

      directly into core.

      Reason more completely about rename-filtering logic in

      narrowfilelog. There could be some surprises lurking there.

      Formally document the narrowspec format. Unify with sparse, if at all

      possible. For bonus points, unify with the server-specified narrowspec

      format.

      narrowrepo.setnarrowpats() or narrowspec.save() need to make sure

      they're holding the wlock.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

Augie Fackler narrow: add a TODO document...	r36121	Integration with the share extension needs improvement. Right now
		we've seen some odd bugs, and the way we modify the contents of the
		.hg/shared file is unfortunate. See wrappostshare() and unsharenarrowspec().

		Resolve commentary on narrowrepo.wraprepo.narrowrepository.status
		about the filtering of status being done at an awkward layer. This
		came up the import to hgext, but nobody's got concrete improvement
		ideas as of then.

		Fold most (or preferably all) of narrowrevlog.py into core.

		Address commentary in narrowrevlog.excludedmanifestrevlog.add -
		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.

		Figure out how to correctly produce narrowmanifestrevlog and
		narrowfilelog instances instead of monkeypatching regular revlogs at
		runtime to our subclass. Even better, merge the narrowing logic
		directly into core.

		Reason more completely about rename-filtering logic in
		narrowfilelog. There could be some surprises lurking there.

		Formally document the narrowspec format. Unify with sparse, if at all
		possible. For bonus points, unify with the server-specified narrowspec
		format.

		narrowrepo.setnarrowpats() or narrowspec.save() need to make sure
		they're holding the wlock.