<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Should a patch for 3.6 be cherry-picked directly from master or from 3.7?  Does it matter?  With hg, double forward merges had to be done linearly, as from 3.6 to 3.7 and thence from 3.7 to 3.8 (master).</span></blockquote><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div>cherry_picker.py and miss-islington will backport from master to newest branch first.</div><div>So master -> 3.7, then master -> 3.6, and master -> 2.7.</div><div>It does not backport from 3.7 -> 3.6.</div><div><br></div><div>When doing it manually yourself, you should be able to backport from master -> 3.6 first and then master -> 3.7, it doesn't matter.</div><div><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">Mariatta Wijaya</div></div>
<br></div></div>