Basically speaking ... one would take the working patch set from trunk and apply it to CC ... fix all the errors, changes, etc. Then once you have a working patch set for CC ... submit it.
A couple of recent examples : https://patchwork.ozlabs.org/patch/505724/ and https://patchwork.ozlabs.org/patch/499956/ Regards Larry On Tue, Sep 29, 2015 at 8:47 PM, Jonathan Bennett <jbscienc...@gmail.com> wrote: > 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. > > --Jonathan Bennett > > On Tue, Sep 29, 2015 at 2:15 PM Drasko DRASKOVIC < > drasko.drasko...@gmail.com> wrote: > >> Hi all, >> how are the patches from main development branch backported to Chaos >> Calmer branch from dev branch? >> >> Do I have to re-post this patch-set >> >> http://git.openwrt.org/?p=openwrt.git;a=commit;h=c84682a79e36bb57f4f78d51aa589f7bfe3fb5e8 >> against this branch: >> http://git.openwrt.org/?p=15.05/openwrt.git;a=summary? >> >> BR, >> Drasko >> _______________________________________________ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >> > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
