<div dir="ltr"><div class="gmail_default" style="font-size:small">Basically speaking ... one would take the working patch set from trunk and apply it to CC ... fix all the errors, changes, etc. </div><div class="gmail_default" style="font-size:small">Then once you have a working patch set for CC ... submit it.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">A couple of recent examples :</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style=""><a href="https://patchwork.ozlabs.org/patch/505724/">https://patchwork.ozlabs.org/patch/505724/</a> and  <a href="https://patchwork.ozlabs.org/patch/499956/">https://patchwork.ozlabs.org/patch/499956/</a><br></div><div class="gmail_default" style=""><br></div><div class="gmail_default" style="">Regards</div><div class="gmail_default" style=""><br></div><div class="gmail_default" style="">Larry</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 29, 2015 at 8:47 PM, Jonathan Bennett <span dir="ltr"><<a href="mailto:jbscience87@gmail.com" target="_blank">jbscience87@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Guys with more experience will certainly be better suited to answer, but from what I've observed, something like new device support wouldn't be appropriate to backport into a released branch.  Usually only critical security patches are backported.  There has been discussion of 15.05 working as a LTS sort of release, with minor version updates, so a 15.05.1 might happen in a few months.  You *might* get your patches included for that maintenance release.  That's certainly not for me to decide, though.<span class="HOEnZb"><font color="#888888"><div><br></div><div>--Jonathan Bennett</div></font></span></div><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote"><div dir="ltr">On Tue, Sep 29, 2015 at 2:15 PM Drasko DRASKOVIC <<a href="mailto:drasko.draskovic@gmail.com" target="_blank">drasko.draskovic@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
how are the patches from main development branch backported to Chaos<br>
Calmer branch from dev branch?<br>
<br>
Do I have to re-post this patch-set<br>
<a href="http://git.openwrt.org/?p=openwrt.git;a=commit;h=c84682a79e36bb57f4f78d51aa589f7bfe3fb5e8" rel="noreferrer" target="_blank">http://git.openwrt.org/?p=openwrt.git;a=commit;h=c84682a79e36bb57f4f78d51aa589f7bfe3fb5e8</a><br>
against this branch:<br>
<a href="http://git.openwrt.org/?p=15.05/openwrt.git;a=summary" rel="noreferrer" target="_blank">http://git.openwrt.org/?p=15.05/openwrt.git;a=summary</a>?<br>
<br>
BR,<br>
Drasko<br>
_______________________________________________<br>
openwrt-devel mailing list<br>
<a href="mailto:openwrt-devel@lists.openwrt.org" target="_blank">openwrt-devel@lists.openwrt.org</a><br>
<a href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel" rel="noreferrer" target="_blank">https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel</a><br>
</blockquote></div>
</div></div><br>_______________________________________________<br>
openwrt-devel mailing list<br>
<a href="mailto:openwrt-devel@lists.openwrt.org">openwrt-devel@lists.openwrt.org</a><br>
<a href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel" rel="noreferrer" target="_blank">https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel</a><br>
<br></blockquote></div><br></div>