From: Vineet Gupta <Vineet.Gupta1@synopsys•com>
To: linux-next <linux-next@vger•kernel.org>,
lkml <linux-kernel@vger•kernel.org>
Cc: Anton Kolesov <Anton.Kolesov@synopsys•com>,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: linux next naive question
Date: Tue, 16 Aug 2016 13:39:55 -0700 [thread overview]
Message-ID: <28b3b6db-bc24-24cb-c5bd-6d46a65d489e@synopsys.com> (raw)
[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
reply other threads:[~2016-08-16 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28b3b6db-bc24-24cb-c5bd-6d46a65d489e@synopsys.com \
--to=vineet.gupta1@synopsys$(echo .)com \
--cc=Anton.Kolesov@synopsys$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox