From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "L. A. Walsh" <lkml@tlinx.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.16-rc1
Date: Fri, 20 Jan 2006 08:47:57 +0000 [thread overview]
Message-ID: <20060120084756.GA23459@flint.arm.linux.org.uk> (raw)
In-Reply-To: <43D09C21.6030607@tlinx.org>
On Fri, Jan 20, 2006 at 12:15:29AM -0800, L. A. Walsh wrote:
> That seems a bit unproductive given the amount of patches
> that get sent to the list. It would be easier for senders
> and, likely, readers to sort through topics if people could
> put patches in 1 post rather than sending 10-20 consecutive
> "[PATCH XX/30]"...
That's not the (main) reason why patches get split up. They're
split up into logical incremental changes to aid review.
Also, you should be able to apply the first half of the patch set
and get a working kernel - this aids debugging since you can find
the small set of changes which caused the problem.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-01-20 8:48 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 8:19 Linux 2.6.16-rc1 Linus Torvalds
2006-01-17 13:16 ` Prakash Punnoor
2006-01-17 13:36 ` Jeff Garzik
2006-01-17 13:49 ` Prakash Punnoor
2006-01-17 16:25 ` Gene Heskett
2006-01-17 18:05 ` Mauro Carvalho Chehab
2006-01-17 20:38 ` Gene Heskett
2006-01-17 17:39 ` Diego Calleja
2006-01-17 18:25 ` Linus Torvalds
2006-01-17 19:06 ` Diego Calleja
2006-01-17 20:08 ` Jan Engelhardt
2006-01-17 21:04 ` Antonio Vargas
2006-01-17 22:05 ` Jan Engelhardt
2006-01-20 8:15 ` L. A. Walsh
2006-01-20 8:28 ` David S. Miller
2006-01-20 8:47 ` Russell King [this message]
2006-01-18 0:22 ` Linux 2.6.16-rc1 -- which gcc version? Jeff Chua
2006-01-18 1:14 ` Linus Torvalds
2006-01-18 7:00 ` Arjan van de Ven
2006-01-19 23:42 ` Linux 2.6.16-rc1 Bill Davidsen
2006-01-17 19:27 ` David R
2006-01-18 4:59 ` Greg KH
2006-01-18 9:28 ` David R
2006-01-18 20:57 ` David R
2006-01-18 21:04 ` Greg KH
2006-01-17 19:54 ` Linux 2.6.16-rc1 - hrtimer hotfix Thomas Gleixner
2006-01-17 20:08 ` Lee Revell
2006-01-17 20:12 ` Thomas Gleixner
2006-01-17 21:06 ` Linux 2.6.16-rc1 Valdis.Kletnieks
2006-01-18 1:41 ` Patrick McHardy
2006-01-17 21:54 ` Eyal Lebedinsky
2006-01-17 23:27 ` Sam Ravnborg
2006-01-18 7:59 ` Jean Delvare
2006-01-18 9:15 ` Sam Ravnborg
2006-01-18 10:01 ` Kurt Wall
2006-01-18 21:10 ` Eyal Lebedinsky
2006-01-19 1:40 ` Kurt Wall
2006-01-18 11:24 ` Eyal Lebedinsky
2006-01-18 12:42 ` Sam Ravnborg
2006-01-18 12:13 ` Jean Delvare
2006-01-18 13:22 ` Jan Engelhardt
2006-01-18 18:12 ` Jean Delvare
2006-01-18 20:14 ` Jan Engelhardt
2006-01-18 20:32 ` Sam Ravnborg
2006-01-18 20:54 ` Bryan O'Sullivan
2006-01-18 21:20 ` Sam Ravnborg
2006-01-18 21:47 ` Bryan O'Sullivan
2006-02-07 12:42 ` Jean Delvare
2006-02-07 16:55 ` Bryan O'Sullivan
2006-01-18 16:15 ` Johannes Stezenbach
2006-01-18 8:44 ` Eyal Lebedinsky
2006-01-27 0:06 ` Linux 2.6.16-rc1 - usb printer problems Helge Hafting
2006-01-27 22:52 ` Greg KH
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=20060120084756.GA23459@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.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