From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753752AbcHPUkP (ORCPT ); Tue, 16 Aug 2016 16:40:15 -0400 Received: from smtprelay.synopsys.com ([198.182.47.9]:39513 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753285AbcHPUkM (ORCPT ); Tue, 16 Aug 2016 16:40:12 -0400 X-Mozilla-News-Host: news://gmane.comp.lib.uclibc.buildroot:119 To: linux-next , lkml CC: Anton Kolesov , Stephen Rothwell From: Vineet Gupta Subject: linux next naive question Message-ID: <28b3b6db-bc24-24cb-c5bd-6d46a65d489e@synopsys.com> Date: Tue, 16 Aug 2016 13:39:55 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.9.131.254] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [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