Message289369
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 https://help.github.com/articles/checking-out-pull-requests-locally/
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:04 | paul.moore | set | recipients:
+ paul.moore, ncoghlan, tim.golden, python-dev, eric.frederich, zach.ware, steve.dower |
2017-03-10 14:42:04 | paul.moore | set | messageid: <1489156924.36.0.97450939303.issue29319@psf.upfronthosting.co.za> |
2017-03-10 14:42:04 | paul.moore | link | issue29319 messages |
2017-03-10 14:42:04 | paul.moore | create | |
|