Message182633
| Author |
terry.reedy |
| Recipients |
chris.jerdonek, eric.araujo, ezio.melotti, ncoghlan, pitrou, sandro.tosi, terry.reedy, tshepang |
| Date |
2013年02月22日.05:30:53 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1361511053.51.0.635494766926.issue14468@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Do you you mean s/update/clone/? duh, yes
> I don't think the devguide should cover tortoisehg.
Given the obnoxiousness of Command Prompt, and how foreign it is to working on Windows, I think maybe there should be an addendum *somewhere*, but I don't expect anyone else to write it. (Goodness, there is a devguide chapter for emacs editing.) The easiest way to run direct hg commands is within the command pane of Workbench.
About "run `make patchcheck`". The current Committing page gives
"(or ./python.exe Tools/scripts/patchcheck.py on Windows)" as the windows equivalent. './' does not work on Windows. '.\' will, but I do not know if it is needed. I presume the command should be given from within a particular repository. In its top directory, 'python' will run the installed python, 'PCbuild\python.exe' or 'PCbuild\python_d.exe' (backslash required here, though not in the patchcheck path) is needed to run the python built from that repository. |
|