[LEDE-DEV] proper protocol for submitting patches that should be upstreamed as well?

[Hartmut Knaack]

rpjday at crashcourse.ca schrieb am 28.08.2017 um 14:15:
> 
>    been away from openwrt for a while, just jumped back in with LEDE, so
> will have a few questions shortly, but this one should(?) be simple.
> 
>    the recipe for submitting patches for LEDE looks pretty straightforward,
> but is there anything special that needs to be done if said patch should
> also be upstreamed for that package?
> 

Like mentioned in target/linux/generic/PATCHES:
All patches should be named 'NNN-lowercase_shortname.patch'
and sorted into the following categories:
0xx - upstream backports
1xx - code awaiting upstream merge

So, you would send your patch upstream and with the 1xx prefix to LEDE. In
case of recommended changes from the upstream project, it would be great to
keep your patch at LEDE in sync. As soon as it gets applied to upstream,
you should move it into the 0xx category here, as well, and later remove
it, when the new upstream version is used by LEDE.
This is for kernel patches, so for other packages, there may be different
prefix systems, but you get the point. Write a descriptive commit message
and try to maintain your patch as much as possible.