From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Keith Packard <keithp@keithp.com>
Cc: "drivers, Intel" <Intel-gfx@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] drivers/drm/i915 maintenance process
Date: Mon, 6 Jun 2011 16:43:35 -0700 [thread overview]
Message-ID: <20110606164335.10bdea9d@jbarnes-desktop> (raw)
In-Reply-To: <20110606163025.5b1bfdee@jbarnes-desktop>
On Mon, 6 Jun 2011 16:30:25 -0700
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Mon, 06 Jun 2011 16:24:46 -0700
> Keith Packard <keithp@keithp.com> wrote:
>
> > On Mon, 6 Jun 2011 13:36:18 -0700, Jesse Barnes <jbarnes@virtuousgeek.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. :)
Oh and the other big reason is testing. rebase generally voids
previous testing since you have new bits, so Linus really hates to see
a rebase just before a pull request, and I think Dave does too.
But rebasing for good reason (e.g. to make your -next branch a superset
of your -fixes branch) on occasion is fine.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2011-06-06 23:50 UTC|newest]
Thread overview: 7+ 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
2011-06-06 20:36 ` Jesse Barnes
2011-06-06 23:24 ` Keith Packard
2011-06-06 23:30 ` Jesse Barnes
2011-06-06 23:43 ` Jesse Barnes [this message]
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=20110606164335.10bdea9d@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).