From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S969621AbdAEWxR (ORCPT ); Thu, 5 Jan 2017 17:53:17 -0500 Received: from ozlabs.org ([103.22.144.67]:45831 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934031AbdAEWxF (ORCPT ); Thu, 5 Jan 2017 17:53:05 -0500 Date: Fri, 6 Jan 2017 09:50:40 +1100 From: Stephen Rothwell To: Maxime Ripard Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: failure fetching the sunxi tree Message-ID: <20170106095033.0fb9661c@canb.auug.org.au> In-Reply-To: <20170105151523.vec6dnldfbkce2mk@lukather> References: <20161221092413.3b1b1f75@canb.auug.org.au> <20170104093124.24147e05@canb.auug.org.au> <20170105151523.vec6dnldfbkce2mk@lukather> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Maxime, On Thu, 5 Jan 2017 16:15:23 +0100 Maxime Ripard wrote: > > Sorry, I went in holidays and removed that branch to avoid any > conflicts during the merge window... I didn't know it was an issue to To do that in the future, just set your branch to point somewhere in Linus' tree (or whatever upstream you use). > you and assumed that you would just ignore it, sorry for that, it > won't happen again. I do fetch the branches every morning. Its not a big problem as if I get an error, I just use whatever I had previously fetched. > Anyway, I just pushed a new one, so everything should be back to > normal. Thanks. -- Cheers, Stephen Rothwell