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:	Mon, 6 Jun 2011 16:30:25 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Keith Packard <keithp@...thp.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 Mon, 06 Jun 2011 16:24:46 -0700
Keith Packard <keithp@...thp.com> wrote:

> On Mon, 6 Jun 2011 13:36:18 -0700, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
> 
> > Can you keep drm-intel-next fairly up to date with respect to the fixes
> > branch?  I.e. keep it a superset of drm-intel-fixes for the most part?
> 
> Yes, I wanted to do that now, but -fixes is not a fast-forward from
> -next and I thought I shouldn't be doing rebases.

You shouldn't if your downstream is using git trees and you're pulling
from them, but it depends on your downstream.  In my particular case,
I'm ok with rebases if it means I get fixes. :)

-- 
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/