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 paul.moore
Recipients eric.frederich, ncoghlan, paul.moore, python-dev, steve.dower, tim.golden, zach.ware
Date 2017-03-10.14:42:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for that Steve. I had a recollection that there's a way of referencing the PR itself as a branch within the main repo (I guess it must *be* a branch, as how otherwise would github be able to do things like get Travis to build it?) but I don't recall the details.

Hmm, a bit of googling later I found

git fetch origin pull/ID/head:BRANCHNAME

And indeed that works - I checked out Nick's patch like that. I'd still need to merge it into the 3.6 branch, which is another set of git commands I don't yet know (cherry-pick, maybe?)
Date User Action Args
2017-03-10 14:42:04paul.mooresetrecipients: + paul.moore, ncoghlan, tim.golden, python-dev, eric.frederich, zach.ware, steve.dower
2017-03-10 14:42:04paul.mooresetmessageid: <>
2017-03-10 14:42:04paul.moorelinkissue29319 messages
2017-03-10 14:42:04paul.moorecreate