On Wed, Sep 10, 2014 at 12:27 AM, Lupe Christoph <[email protected]> wrote: > On Wednesday, 2014-09-10 at 03:52:29 +0800, Weijie Gao wrote: >> On 2014/9/10 3:11, Lupe Christoph wrote: > >> >Don't put the patch in the mail body, if the mail client doesn't corrupt >> >it, some other intermediate software may still do that. Send patches as >> >attachments, as a text file or in a ZIP archive (or tar.gz). > >> Thanks. > >> Then can I still send a email with attachments >> [email protected]? >> This is the first time I submit a patch. > > I think you caught me there - I assumed this should work. > > But actually I believe you should be asking if you should submit a patch > via this mailing list at all. I think it would be better to open a ticket > on https://dev.openwrt.org/ and attach your patch to it. > > If you want to discuss what your patch does and why you want to submit > it first, this mailing list would be a good place. But if you're sure > about it, just opening a ticket would be fine.
Please don't open tickets for patches, tickets are reserved for bugs. See https://dev.openwrt.org/wiki/SubmittingPatches about how to submit patches to OpenWrt. It also has a note about email clients. Patches for the external feeds (packages, routing, management) need to be submitted through a pull request on github. We don't accept patches for the oldpackages feed. Jonas _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
