From: "David S. Miller" <davem@davemloft.net>
To: Dave Airlie <airlied@linux.ie>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: maintaining DRM and using bitkeeper..
Date: Fri, 27 Aug 2004 17:09:51 -0700 [thread overview]
Message-ID: <20040827170951.3ad3900e.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0408280046220.23054@skynet>
On Sat, 28 Aug 2004 00:54:06 +0100 (IST)
Dave Airlie <airlied@linux.ie> wrote:
> 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...)
No, this will look perfectly fine. This is exactly how things are
supposed to work.
When you ask for a pull, you can just concatenate the individual changesets
as patches, and it looks really nice. That is what I do when I send a pull
request to Marcelo or Linus.
prev parent reply other threads:[~2004-08-28 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 23:57 maintaining DRM and using bitkeeper 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
2004-08-28 0:09 ` David S. Miller [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=20040827170951.3ad3900e.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=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 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.