[<prev] [next>] [day] [month] [year] [list]
Message-ID: <28b3b6db-bc24-24cb-c5bd-6d46a65d489e@synopsys.com>
Date: Tue, 16 Aug 2016 13:39:55 -0700
From: Vineet Gupta <Vineet.Gupta1@...opsys.com>
To: linux-next <linux-next@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>
CC: Anton Kolesov <Anton.Kolesov@...opsys.com>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: linux next naive question
[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
Powered by blists - more mailing lists