All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Dave Airlie <airlied@redhat.com>
Cc: dri-devel@lists.freedesktop.org, "drivers\,
	Intel" <Intel-gfx@lists.freedesktop.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: drivers/drm/i915 maintenance process
Date: Sun, 05 Jun 2011 13:16:38 -0700	[thread overview]
Message-ID: <yunlixg2fvd.fsf@aiko.keithp.com> (raw)
In-Reply-To: <1307255026.17387.8.camel@t60prh>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

On Sun, 05 Jun 2011 16:23:43 +1000, Dave Airlie <airlied@redhat.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@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Keith Packard <keithp@keithp.com>
To: Dave Airlie <airlied@redhat.com>
Cc: dri-devel@lists.freedesktop.org, "drivers,
	Intel" <Intel-gfx@lists.freedesktop.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: drivers/drm/i915 maintenance process
Date: Sun, 05 Jun 2011 13:16:38 -0700	[thread overview]
Message-ID: <yunlixg2fvd.fsf@aiko.keithp.com> (raw)
In-Reply-To: <1307255026.17387.8.camel@t60prh>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

On Sun, 05 Jun 2011 16:23:43 +1000, Dave Airlie <airlied@redhat.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@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2011-06-05 20:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05  6:05 drivers/drm/i915 maintenance process Keith Packard
2011-06-05  6:23 ` Dave Airlie
2011-06-05 20:16   ` Keith Packard [this message]
2011-06-05 20:16     ` Keith Packard
2011-06-06 20:36 ` Jesse Barnes
2011-06-06 20:36   ` Jesse Barnes
2011-06-06 23:24   ` Keith Packard
2011-06-06 23:24     ` Keith Packard
2011-06-06 23:30     ` Jesse Barnes
2011-06-06 23:30       ` Jesse Barnes
2011-06-06 23:43       ` [Intel-gfx] " Jesse Barnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yunlixg2fvd.fsf@aiko.keithp.com \
    --to=keithp@keithp.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.