From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753058AbaATKiL (ORCPT ); Mon, 20 Jan 2014 05:38:11 -0500 Received: from smtp02.citrix.com ([66.165.176.63]:57304 "EHLO SMTP02.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752372AbaATKiJ (ORCPT ); Mon, 20 Jan 2014 05:38:09 -0500 X-IronPort-AV: E=Sophos;i="4.95,689,1384300800"; d="scan'208";a="92350801" Message-ID: <52DCFC8F.1050607@citrix.com> Date: Mon, 20 Jan 2014 10:38:07 +0000 From: David Vrabel User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121215 Iceowl/1.0b1 Icedove/3.0.11 MIME-Version: 1.0 To: "Luis R. Rodriguez" CC: , Konrad Rzeszutek Wilk , Stephen Rothwell , Subject: Re: MAINTAINERS tree branches [xen tip as an example] References: <20140117230219.GA28413@garbanzo.do-not-panic.com> In-Reply-To: <20140117230219.GA28413@garbanzo.do-not-panic.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.2.76] X-DLP: MIA2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/01/14 23:02, Luis R. Rodriguez wrote: > As per linux-next Next/Trees [0], and a recent January MAINTAINERS patch [1] > from David one of the xen development kernel git trees to track is > xen/git.git [2], this tree however gives has undefined references when doing a > fresh clone [shown below], but as expected does work well when only cloning > the linux-next branch [also below]. While I'm sure this is fine for > folks who can do the guess work do we really want to live with trees like > these on MAINTAINERS ? The MAINTAINERS file doesn't let us specify branches > required, so perhaps it should -- if we want to live with these ? Curious, how > many other git are there with a similar situation ? We don't recommend doing development work for the Xen subsystem based on xen/tip.git so I think it's fine to have to checkout the specific branch you are interested in. > The xen project web site actually lists [3] Konrad's xen git tree [4] for > development as the primary development tree, that probably should be > updated now, and likely with instructions to clone only the linux-next > branch ? I've updated the wiki to read: For development the recommended branch is: The mainline Linus linux.git tree. To see what's queued for the next release, the next merge window, and other work in progress: The Xen subsystem maintainers' tip.git tree. David