From: Jiri Kosina <jkosina@suse.cz>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: benh@kernel.crashing.org,
ksummit-2008-discuss@lists.linux-foundation.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Request for discussion on when to merge drivers
Date: Thu, 19 Jun 2008 01:48:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.1.10.0806190143230.4593@jikos.suse.cz> (raw)
In-Reply-To: <1213832399.3515.109.camel@localhost.localdomain>
On Wed, 18 Jun 2008, James Bottomley wrote:
> Arguably, I can do this by putting it into my upstream tree (which feeds
> into linux-next) the reason for not doing so is that Linus likes us to
> preserve history in there when we can.
This of course applies only for branches/trees for which there are
downstream git users.
If the only reason you merge the driver into your tree is to have it
propagated into linux-next, you could very well create a separate branch
for it, and pull this branch into the one linux-next pulls from you (I
guess you have a dedicated branch for linux-next which is safe to be
rebased by definition, right?).
> If I need to pull the driver for a reroll it really screws the git
> history
But not in any of the branches that have upstream git users.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2008-06-18 23:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 15:27 James Bottomley
2008-06-18 17:15 ` [Ksummit-2008-discuss] " Luck, Tony
2008-06-18 17:34 ` James Bottomley
2008-06-18 17:30 ` Benny Halevy
2008-06-18 23:20 ` [Ksummit-2008-discuss] " Jiri Kosina
2008-06-19 7:34 ` Benny Halevy
2008-06-18 18:38 ` Mauro Carvalho Chehab
2008-06-18 23:31 ` Benjamin Herrenschmidt
2008-06-18 23:39 ` [Ksummit-2008-discuss] " James Bottomley
2008-06-18 23:48 ` Jiri Kosina [this message]
2008-06-19 9:13 ` Stefan Richter
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=alpine.LNX.1.10.0806190143230.4593@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=James.Bottomley@hansenpartnership.com \
--cc=benh@kernel.crashing.org \
--cc=ksummit-2008-discuss@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®