From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 9B16778369 for ; Mon, 14 Aug 2017 21:44:16 +0000 (UTC) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.15.2/8.15.2/Debian-3) with ESMTPSA id v7ELiGpC023599 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 14 Aug 2017 22:44:17 +0100 Message-ID: <1502747056.13978.40.camel@linuxfoundation.org> From: Richard Purdie To: "Slater, Joseph" , "openembedded-core@lists.openembedded.org" Date: Mon, 14 Aug 2017 22:44:16 +0100 In-Reply-To: <007BD92917A2324FA403BCF9A464CF84CF3D645F@ALA-MBD.corp.ad.wrs.com> References: <007BD92917A2324FA403BCF9A464CF84CF3D645F@ALA-MBD.corp.ad.wrs.com> X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (dan.rpsys.net [192.168.3.1]); Mon, 14 Aug 2017 22:44:17 +0100 (BST) X-Virus-Scanned: clamav-milter 0.99.2 at dan X-Virus-Status: Clean Subject: Re: master-next X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Aug 2017 21:44:18 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit On Mon, 2017-08-14 at 19:24 +0000, Slater, Joseph wrote: > Is there something “different” about this branch?  I find that if I > have a local master and master-next, and am on master, when I do a > pull master-next will wind up both ahead and behind origin/master- > next.  If I switch to master-next and rebase, it might fail, or it > might leave me with one or more “local” commits that are not mine.   > For the case I tried today, it is commit 3d4f241 which seems to only > be on my local master-next, but came from Mark Horn/Ross Burton on > August 2. >   > Can anyone explain this? master-next rebases. The patch in question was in master-next, it failed tests and I booted it out until it gets fixed. master never rebases by comparison. Cheers, Richard