From: Roland Dreier <rdreier@cisco.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/90] Post 2.6.21 OMAP update
Date: Thu, 05 Apr 2007 11:29:23 -0700 [thread overview]
Message-ID: <adaslbe8ykc.fsf@cisco.com> (raw)
In-Reply-To: <20070405180334.GW24297@atomide.com> (Tony Lindgren's message of "Thu, 5 Apr 2007 14:03:36 -0400")
> Hmm, yeah I'll see if I could group them a bit. The problem there
> is that the patch series contains multiple rounds of "add and fix"
> cycles. Pretty much all the non-dependant fixes have already been
> applied, BTW.
I think it's nice to roll up fixes into patches that haven't been
merged upstream yet. For example I try to avoid merging series like
Add feature A
Add feature B
Fix 1 for feature A
Fix 2 for feature A
Fix for fix 1 for feature A
because that means I already knew the first patch was broken before it
ever got merged. And it's better to avoid setting any more booby
traps for people trying to use git bisect or something like
that... enough bugs get merged by accident without us merging known
bugs. So before I merge, I go back and create a new series like
Add fixed feature A
Add feature B
- R.
next prev parent reply other threads:[~2007-04-05 18:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 17:46 [PATCH 0/90] Post 2.6.21 OMAP update Tony Lindgren
2007-04-04 17:46 ` [PATCH 1/90] ARM: OMAP: Place SMS and SDRC into smart idle mode Tony Lindgren
2007-04-04 17:46 ` [PATCH 2/90] ARM: OMAP: Force APLLs always active Tony Lindgren
2007-04-04 17:46 ` [PATCH 3/90] ARM: OMAP: Add DMA IRQ sanity checks Tony Lindgren
2007-04-04 17:46 ` [PATCH 4/90] ARM: OMAP: Enable 24xx GPIO autoidling Tony Lindgren
2007-04-04 17:46 ` [PATCH 5/90] ARM: OMAP: Add function to print clock usecounts Tony Lindgren
2007-04-04 17:46 ` [PATCH 6/90] ARM: OMAP: Enable serial idling and wakeup features Tony Lindgren
2007-04-04 17:46 ` [PATCH 7/90] ARM: OMAP: Optimize INTC register accesses and enable autoidling Tony Lindgren
2007-04-04 17:46 ` [PATCH 8/90] ARM: OMAP: FB: add controller platform data Tony Lindgren
2007-04-04 18:27 ` [PATCH 0/90] Post 2.6.21 OMAP update Tony Lindgren
2007-04-04 18:39 ` Randy Dunlap
2007-04-04 18:44 ` Tony Lindgren
2007-04-04 21:44 ` Alan Cox
2007-04-05 13:21 ` Tony Lindgren
2007-04-05 16:31 ` Roland Dreier
2007-04-05 18:03 ` Tony Lindgren
2007-04-05 18:29 ` Roland Dreier [this message]
2007-04-09 21:45 ` Tony Lindgren
2007-04-05 20:27 ` Alan Cox
2007-04-06 7:18 ` Russell King
2007-04-09 21:49 ` Tony Lindgren
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=adaslbe8ykc.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=tony@atomide.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