linux-kernel - Re: drivers/drm/i915 maintenance process

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 05 Jun 2011 13:16:38 -0700
From:	Keith Packard <keithp@...thp.com>
To:	Dave Airlie <airlied@...hat.com>
Cc:	dri-devel@...ts.freedesktop.org,
	"drivers\, Intel" <Intel-gfx@...ts.freedesktop.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: drivers/drm/i915 maintenance process

On Sun, 05 Jun 2011 16:23:43 +1000, Dave Airlie <airlied@...hat.com> wrote:

> So when Linus is releasing rc4/5 you should really be cutting down stuff
> going into your -next, and getting the tree ready for me to take. We can
> probably add your tree direct to the -next git list as well so that we
> can get the benefits of -next testing earlier.

Right, even earlier than I had thought. That should be pretty easy to follow.

> Just make sure any merge commits are documented in the commit, this
> generally means having to git commit --amend the merge commit since most
> of the time it doesn't allow you to write anything unless you get a
> conflict, esp if its a strange non i915 commit (like say some ACPI or
> bluetooth commit that fixes a test laptop).

Thanks for your comments; I'll try to have -next ready by rc4/rc5 time
this release.

-- 
keith.packard@...el.com

Content of type "application/pgp-signature" skipped