Date: Thu, 14 Feb 2008 15:38:50 -0200
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: first tree
Message-ID: <20080214153850.486f8205@gaivota>
In-Reply-To: <20080215003537.8911ce35.sfr@canb.auug.org.au>
References: <20080215003537.8911ce35.sfr@canb.auug.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1023
Lines: 29


> The tree currently contains:
> 	Greg's driver-core, pci and usb quilt series (in that order)
> 	Alasdair Kergon's device-mapper quilt tree
> 	Jiri Kosina's hid git tree
> 	Jean Delvare's i2c quilt tree
> 	Randy Dunlap's kernel-doc quilt tree
> 	Haavard Skinnemoen's avr32 git tree

Please add v4l-dvb tree, at:

ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git

The above tree has two branches: 'master' and 'stable'

Both branches will have V4L/DVB next patches. The first is against your master,
and the second, against your stable.

I've opted to have both trees, since probably 'stable' is the better option for
you to clone. On the other hand, 'master' allow me to foresee if an "alien"
patch would conflict with a subsystem patch.

Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/