[issue20265] Bring Windows docs up to date

Zachary Ware report at bugs.python.org
Thu Mar 13 15:29:14 CET 2014


Zachary Ware added the comment:

Éric Araujo wrote:
> From #20265:

Correction, this is #20265, that message was from #20266 :)

Kathleen: both Éric and I have left some review comments for you in Rietveld, which should have sent you an email with the comments and links to the Rietveld review.

Also, if you're having end-of-line issues, I would recommend turning on the Mercurial eol extension (either edit "%userprofile%\Mercurial.ini" manually, or use the Extensions section of File -> Settings... from TortoiseHg Workbench).  To work most effectively, you'll need to update to the 'null' revision, then update back to default after turning on eol.  That will ensure that most files have \r\n line endings and hg can keep line endings straight for you thereafter.

Here's a sample of my Mercurial.ini with some other things you may be interested in:

[extensions]
;keep eols straight
eol=

;delete untracked files (helps with starting from a clean slate)
purge=

;colorize output, including making trailing whitespace visible in diffs
color=

;create several clones that share history, useful for keeping
;separate clones per branch without having to pull individually
share=

[defaults]
;don't try to commit when importing a patch
import = --no-commit

----------
title: Bring Doc/using/windows up to date -> Bring Windows docs up to date

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20265>
_______________________________________


More information about the Python-bugs-list mailing list