* linux next naive question
@ 2016-08-16 20:39 Vineet Gupta
0 siblings, 0 replies; only message in thread
From: Vineet Gupta @ 2016-08-16 20:39 UTC (permalink / raw)
To: linux-next, lkml; +Cc: Anton Kolesov, Stephen Rothwell
[Now in plain text]
Hi Stephan,
For preparing linux-next is there a specific merge strategy / script foo for
pulling branches from same developers repo. So for ARC there's for-curr and
for-next, and a lot of times they might have potentially conflicting changes, base
lines etc. It seem in linux-next for-curr is added first and then for-next - a
very likely case is for-next being significantly behind for-curr with a few
straggler changes.
The reason I ask is we want to implement something similar in our existing
regression setup - which builds / boot/ test jobs on several platforms but
currently only uses my kernel.org repo's for-next - I want to expose both the
branches w/o having to explicitly replicate duplicate changes in my for-next from
for-curr
Thx,
-Vineet
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-08-16 20:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-08-16 20:39 linux next naive question Vineet Gupta
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox