From: Dave Airlie <airlied@linux.ie>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: maintaining DRM and using bitkeeper..
Date: Sat, 28 Aug 2004 00:54:06 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.58.0408280046220.23054@skynet> (raw)
In-Reply-To: <20040827173807.GB7445@mars.ravnborg.org>
>
> Another thing you should realise is that flag-day patches are NOT welcome.
> The ongoing effort removing macors are better included in the kernel as 20
> small steps rather than 1 big patch.
This is my main issue with using bitkeeper vs separate patches, if I check
the macro conversion into bitkeeper as separate patches each removing a
couple of inter-related macros (this is my intention... it is what I did
in the DRM CVS tree) and I ask Linus to pull it from a tree, will it not
look like one big patch (albeit in a number of changesets...) - so the
patch itself will look like a flag day but the bk pull will look like a
set of patches... whereas without bk I send 20 patches to LK in 20 mails
they are nice and separated out ..
>
> May I ask why not?
well they are down the patch queue and will take me a bit of time to sort
out if the patches in front don't make it in ... though I might get to it
soon..
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person
next prev parent reply other threads:[~2004-08-27 23:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 23:57 Dave Airlie
2004-08-27 0:59 ` David S. Miller
2004-08-27 1:11 ` Dave Airlie
2004-08-27 17:38 ` Sam Ravnborg
2004-08-27 23:54 ` Dave Airlie [this message]
2004-08-28 0:09 ` David S. Miller
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=Pine.LNX.4.58.0408280046220.23054@skynet \
--to=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®