[LEDE-DEV] RFC: splitting up the patches folder

[John Crispin]

On 21/12/2016 08:50, Álvaro Fernández Rojas wrote:
> Hi John,
> 
> I really like the idea.
> Are you thinking on applying this for generic patches only or also for target specific ones?
> 
> Álvaro.

all patches/ folder whether generic, target or package are controlled by
the same code inside include/quilt.mk so it would work ootb on all 3
types of folders

	John



> El 20/12/16 a las 21:53, John Crispin escribió:
>> Hi,
>>
>> i have been thinking of how to split up the kernel patches folder in a
>> better way. for a start we have all the backports inside the same folder
>> as our normal patches, unfortunately we have some backports and patches
>> that have in the meantime been sent upstream not numbered as 0xx-*.patch.
>>
>> i was thinking that we could add a backports-4.4 which would hold all
>> the backported patches.
>>
>> we could then split up the remaining patches into those that still need
>> to be sent upstream and those that we wont be able to send upstream. the
>> order in which we apply them would then be
>>
>> * backports
>> * pending patches
>> * lede patches
>>
>> this would make going to a newer version easier as they are already
>> ordered correctly and makes it more obvious how big the queue is.
>>
>> 	John
>>
>> _______________________________________________
>> Lede-dev mailing list
>> Lede-dev at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/lede-dev
>>