From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>
Cc: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>,
Netdev <netdev@oss.sgi.com>,
prism54-devel@prism54.org
Subject: Re: [Prism54] CVS -> bk tree update
Date: Tue, 15 Jun 2004 23:10:28 -0400 [thread overview]
Message-ID: <40CFBA24.7030307@pobox.com> (raw)
In-Reply-To: <20040616022008.GM6253@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> Thanks Jeff. I did, and a diff of Andrew's -mm tree Vs our cvs tree
> 2.6.7-prism54 gives a 1898 line diff. This is excluding spaces,
> newlines, and tabbing and all of Andew's .orig, .rej's.
>
> This time it's going to be a *real* pain to provide a changelog and split the
> diffs.. so can I just send you that 1898 line diff and then another for
> space changes? Everything has already been reviewed on the lists here...
>
> I promise this will be our last big patch too. I'll ask our team
> to send patches from now on to netdev after each ChangeLog entry, for
> more public review and to not loose sync of our trees. Let us know if
> you think we should do otherwise.
Sorry, no. You knew that split-up patches would be needed, once the
initial driver merge is complete (which was complete before the most
recent series of 17 patches).
This is one of the big downsides to developing in CVS, and it bites
people again and again.
Linux kernel development relies on split-up patches for review, testing,
and narrowing down which patch in a series introduced a bug. There
are real, engineering-related reasons we do things this way.
Jeff
next prev parent reply other threads:[~2004-06-16 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 19:16 [Prism54] CVS -> bk tree update Luis R. Rodriguez
2004-06-14 22:31 ` Jeff Garzik
2004-06-16 2:20 ` Luis R. Rodriguez
2004-06-16 3:10 ` Jeff Garzik [this message]
2004-06-16 5:11 ` Luis R. Rodriguez
2004-06-16 6:43 ` Luis R. Rodriguez
2004-06-16 20:22 ` Francois Romieu
2004-06-16 20:30 ` Jeff Garzik
2004-06-16 21:09 ` Jeff Garzik
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=40CFBA24.7030307@pobox.com \
--to=jgarzik@pobox.com \
--cc=mcgrof@ruslug.rutgers.edu \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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).