Update on Patch and mirroring KernelCI code
Don Brown <don.f.brown@...>
toggle quoted messageShow quoted text
I like the change to the patch and I'll incorporate it tonight.
We are already mirroring the KernelCI Backend and Frontend and I had almost the exact same thought this weekend that we already need to modify the code to get ours working. I don't mind doing this in the short term. However, this can be a slippery slope since we could easily get to the point where we've essentially forked their code.
I would prefer to work with the KernelCI upstream to incorporate our modifications into their code for the long-term.
On Mon, Jan 23, 2017 at 7:00 AM, <cip-dev-request@...> wrote:
Send cip-dev mailing list submissions to
Daniel Wagner <daniel.wagner@...>
On 01/23/2017 01:39 PM, Don Brown wrote:
I like the change to the patch and I'll incorporate it tonight.Great.
We are already mirroring the KernelCI Backend and Frontend and I hadI agree. There needs to be some strict rules for applying patches.
I would prefer to work with the KernelCI upstream to incorporate ourOkay, understood. What about introducing a default configuration that
clones for upstream but it could be overwritten as config option?