On Tue, 16 Aug 2011, Nicolas Pitre wrote: > On Tue, 16 Aug 2011, Arnd Bergmann wrote: > > > On Sunday 14 August 2011, Olof Johansson wrote: > > > > > > Hi Arnd, > > > > > > Please pull the first set of tegra/board patches for 3.2: > > > > > > > > > The following changes since commit e6a99d312687a42c077a9b8cb5e757f186edb1b9: > > > > > > Merge branch 'slab/urgent' of > > > git://git.kernel.org/pub/scm/linux/kernel/git/penberg/slab-2.6 > > > (2011-08-09 08:42:16 -0700) > > > > > > are available in the git repository at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/olof/tegra.git boards-for-3.2 > > > > > > > Hi Olof, > > > > The contents all look good, but I'm undecided whether we should have > > branches that are not based on a -rc release. In your case, it's > > halfway between -rc1 and -rc2. > > > > Do others have an opinion? If we decide to take development branches > > only when they are based on a proper -rc, I'll do the simple rebase > > of the patches and push them out, otherwise I'll push them as they are. > > Although this might be a nicety, I personally don't particularly care > about the base being set on a tag. I think that keeping the original > committer info intact is more valuable. Right. In general having a devel branch based on a tag is a good thing, but as long as it's not some random commit from the middle of the merge window, it's fine. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
