Re: MAINTAINERS tree branches [xen tip as an example]
From: David Vrabel
Date: Mon Jan 20 2014 - 14:02:50 EST
On 20/01/14 18:33, Luis R. Rodriguez wrote:
> On Mon, Jan 20, 2014 at 2:38 AM, David Vrabel <david.vrabel@xxxxxxxxxx> wrote:
>> On 17/01/14 23:02, Luis R. Rodriguez wrote:
>>> As per linux-next Next/Trees , and a recent January MAINTAINERS patch 
>>> from David one of the xen development kernel git trees to track is
>>> xen/git.git , 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.
> OK thanks.
>>> The xen project web site actually lists  Konrad's xen git tree  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.
> Is the delta of what is queued for the next release typically small?
> Otherwise someone doing development based on linux.git alone should
> have conflicts with anything on the queue, no?
We've not had any issues so far.
>> 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.
> That's the thing, you can't clone the tip.git tree today well, there
> are undefined references and git gives up, asking for the linux-next
> branch however did work.
I think it did work, you just needed to checkout a branch manually.
But it looks like Konrad has pushed a master branch recently, as well.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/