That official submission policy is a bit outdated and we intend to update it at some point.
Due to the issues with email clients and inline patches being mangled more often than not, the current best method that works no matter what is to create a ticket in Trac, attach your patch(es) to it, and refer to it when discussing the patch on the mailing list. The mailing list also handles MIME attachments reasonably well, so that is another alternative - but the Trac interface is superior, especially if the initial patch needs updating or rerolling and such since it is much easier to follow the timeline of patch posts related to a single issue, in contrast to hunting the list for them and hoping to find the most recent. On Tue, 2010-03-23 at 10:37 +0000, Oliver Ripka wrote: > Does this policy apply only to new packages or to all patches? > In any case https://dev.openwrt.org/wiki/SubmittingPatches suggests that > patches should be submitted to the mailing list. > > Oliver > > According to Travis Kemen on Mon, Mar 22, 2010 at 07:45:41PM -0500: > > > Added r20376, next time a patch attached to a ticket will suffice. > > > > Travis > _______________________________________________ > openwrt-devel mailing list > [email protected] > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
