From: Eli Carter <eli.carter@inet.com>
To: rob@landley.net
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] Documentation/SendingPatches [2 of 2].
Date: Wed, 11 Jun 2003 15:41:01 -0500 [thread overview]
Message-ID: <3EE793DD.7080408@inet.com> (raw)
In-Reply-To: <200306111618.10329.rob@landley.net>
Rob Landley wrote:
> The bit about log rolling.
>
> --- linux-new/Documentation/SubmittingPatches 2003-06-11 15:54:29.000000000 -0400
> +++ linux-new/Documentation/SubmittingPatches2 2003-06-11 15:54:06.000000000 -0400
> @@ -92,6 +92,16 @@
> complete, that is OK. Simply note "this patch depends on patch X"
> in your patch description.
>
> +In politics, there's a concept called "log rolling", where unrelated
> +amendments are bundled together so that changes people want grease the
> +way for changes they don't. Do not do this. It's annoying.
> +
> +In coding, this sort of thing can be very subtle, such as performance increases
> +that help your new version perform as well as the original while doing more
> +work, but which could also have been applied to the original making it even
> +faster. The linux-kernel guys are very good at taking the chocolate coating
> +and leaving the pill behind. This can be very frustrating to developers, but
> +it's one of the big reasons open source produces such excellent results.
They are also likely to tell _you_ to take the pill out, clean up the
chocolate, and resubmit; and that takes more of _your_ time.
(And I do like that you broke the log rolling change out; very good
object lesson. :) )
Eli
--------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
next prev parent reply other threads:[~2003-06-11 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 20:18 Rob Landley
2003-06-11 20:41 ` Eli Carter [this message]
2003-06-11 21:27 ` Rob Landley
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=3EE793DD.7080408@inet.com \
--to=eli.carter@inet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=torvalds@transmeta.com \
/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®