upstream/mercurial-mirror Files · contrib/vagrant/README.md

fix: determine fixer tool failure by exit code instead of stderr...

fix: determine fixer tool failure by exit code instead of stderr This seems like the more natural thing, and it probably should have been this way to beign with. It is more flexible because it allows tools to emit diagnostic information while also modifying a file. An example would be an automatic code formatter that also prints any remaining lint issues. Differential Revision: https://phab.mercurial-scm.org/D4158

anatoly techtonik - - Load All Authors

File last commit:

r21874:8da01b6e default


                r39003:a009589c

default

Download file

             README.md
        
                    4 lines
            
             | 80 B
            
                | text/x-minidsrc
            
             |
                MarkdownLexer
            
             / contrib / vagrant / README.md
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        anatoly techtonik
    
contrib/vagrant: use Vagrant for running tests on virtual machine...

              r21874
            
      Run Mercurial tests with Vagrant:

      $ vagrant up

      $ vagrant ssh -c ./run-tests.sh

	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

anatoly techtonik contrib/vagrant: use Vagrant for running tests on virtual machine...	r21874	Run Mercurial tests with Vagrant:

		$ vagrant up
		$ vagrant ssh -c ./run-tests.sh