This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kathweaver
Recipients docs@python, eric.araujo, ezio.melotti, kathweaver, python-dev, westley.martinez, zach.ware
Date 2014-03-13.14:40:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <4cd1cc724da44f34a9cb92c0b1c8307d@BLUPR04MB419.namprd04.prod.outlook.com>
In-reply-to <1394720954.62.0.930935518446.issue20265@psf.upfronthosting.co.za>
Content
It was Visual Studio that messed up the end of line feeds, it keep telling me that there was a problem but I didn't know what it meant.  Erik and I were in #pyladies and he really helped me.

As soon as I get done with gym and other mundane errands I will get back on this.

I can't get over how helpful and nice everyone is! <smile>

Sent using OWA for iPhone
________________________________________
From: Zachary Ware <report@bugs.python.org>
Sent: Thursday, March 13, 2014 9:29:14 AM
To: Kathleen Weaver
Subject: [issue20265] Bring Windows docs up to date

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@bugs.python.org>
<http://bugs.python.org/issue20265>
_______________________________________
History
Date User Action Args
2014-03-13 14:40:29kathweaversetrecipients: + kathweaver, ezio.melotti, eric.araujo, docs@python, westley.martinez, python-dev, zach.ware
2014-03-13 14:40:29kathweaverlinkissue20265 messages
2014-03-13 14:40:29kathweavercreate