public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "Eric S. Raymond" <esr@thyrsus.com>, Nicolas Pitre <nico@cam.org>,
	Tom Rini <trini@kernel.crashing.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Albert D. Cahalan" <acahalan@cs.uml.edu>,
	Matthew Wilcox <willy@ldl.fc.hp.com>,
	james rich <james.rich@m.cc.utah.edu>,
	lkml <linux-kernel@vger.kernel.org>,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention?
Date: Fri, 20 Apr 2001 20:08:59 +0100	[thread overview]
Message-ID: <20010420200859.B5510@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010420085148.V13403@opus.bloom.county> <Pine.LNX.4.33.0104201206250.12186-100000@xanadu.home> <20010420125005.B8086@thyrsus.com>
In-Reply-To: <20010420125005.B8086@thyrsus.com>; from esr@thyrsus.com on Fri, Apr 20, 2001 at 12:50:05PM -0400

On Fri, Apr 20, 2001 at 12:50:05PM -0400, Eric S. Raymond wrote:
> Nicolas Pitre <nico@cam.org>:
> > Why not having everybody's tree consistent with themselves and have whatever
> > CONFIGURE_* symbols and help text be merged along with the very code it
> > refers to?  It's worthless to have config symbols be merged into Linus' or
> > Alan's tree if the code isn't there (yet).  It simply makes no sense.

Really, the above issue is down to the sub-architecture maintainers splitting
up their patches into the "one feature, one bug" thing, rather than "one
set of files" (which, incidentally I'm guilty of as well).  That way, when
stuff gets added, you get:

1. The C source changes for that item
2. The configure script stuff for that one item
3. The help text for that one item.

Currently, stuff that comes to me appears mostly as "here's a configure
update", "here's a PCMCIA update", etc.  I'll pull out an instance from
my patch tracking system (sorry, Philip, yours is the first one I found):

Patch 413/1 (see http://www.arm.linux.org.uk/developer/patches/?id=413/1&mode=patch)
This patch adds the defconfig file for the CLPS7500 architecture, and it
contains symbols such as:

	CONFIG_BLK_DEV_FLD7500
	CONFIG_CLPS7500_FLASH

Neither of these two drivers are currently in Linus' tree, or in fact my
tree.  Should I reject the patch?  Should I accept it and edit these out,
or what?

> And now it has a cost, too.  It makes finding real bugs more difficult.

Well, if they get removed in Linus tree, then when I next sync, they'll get
re-added, or maybe they won't.  Then someone else will remove them, then
they'll get re-added ad infinitum.

This also touches on another issue - patch.  I've had several times where
I've sent Alan stuff, its gone up to Linus, I receive it back, and during
the merge, patch does its stuff without complaining (because there is not
enough context in the diff).  Typically, this happens in the Configure.help
file.

Generally it seems like diff needs to produce one more line of context, and
most of these problems will go away.  Yes, there will still be the odd
problem, so then it becomes the "how much do you crank the setting" problem.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

  reply	other threads:[~2001-04-20 19:10 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20  2:36 OK, let's try cleaning up another nit. Is anyone paying attention? Matthew Wilcox
2001-04-20  3:00 ` Eric S. Raymond
2001-04-20  3:17   ` Matthew Wilcox
2001-04-20  4:07     ` james rich
2001-04-20  4:19       ` Matthew Wilcox
2001-04-20  4:52         ` Albert D. Cahalan
2001-04-20  5:17           ` Rik van Riel
2001-04-20 13:13           ` [parisc-linux] " Alan Cox
2001-04-20 13:35             ` Eric S. Raymond
2001-04-20 13:43               ` Alan Cox
2001-04-20 13:53                 ` Eric S. Raymond
2001-04-20 14:03                   ` Alan Cox
2001-04-20 14:19                     ` Eric S. Raymond
2001-04-20 14:44                       ` Alan Cox
2001-04-20 14:59                         ` Eric S. Raymond
2001-04-20 15:51                           ` Tom Rini
2001-04-20 16:06                             ` Jeff Garzik
2001-04-20 16:15                               ` Bob McElrath
2001-04-20 16:21                                 ` Matthew Wilcox
2001-04-20 19:00                                   ` Jeff Dike
2001-04-20 18:47                                     ` Matthew Wilcox
2001-04-20 21:55                                       ` Jeff Dike
2001-04-20 18:53                                     ` Jes Sorensen
2001-04-20 16:26                                 ` Jeff Garzik
2001-04-20 16:35                             ` Nicolas Pitre
2001-04-20 16:50                               ` Eric S. Raymond
2001-04-20 19:08                                 ` Russell King [this message]
2001-04-21  3:08                                   ` Tom Leete
2001-04-21  8:53                                     ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone rmk
2001-04-20 18:20                               ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? Tom Rini
2001-04-20 18:48                                 ` Nicolas Pitre
2001-04-20 18:55                                   ` Tom Rini
2001-04-20 21:19                                   ` David Woodhouse
2001-04-20 21:24                                     ` Eric S. Raymond
2001-04-20 21:29                                     ` David Woodhouse
2001-04-20 21:35                                       ` Eric S. Raymond
2001-04-20 22:53                                         ` Alan Cox
2001-04-21  0:37                                           ` Eric S. Raymond
2001-04-21 23:39                                             ` Jes Sorensen
2001-04-21 12:32                                           ` David Woodhouse
2001-04-23 21:12                                             ` [patch] fix broken symbols (was Re: OK, let's try ...) Arjan van de Ven
2001-04-20 21:39                                       ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? David Woodhouse
2001-04-21  0:24                                         ` Eric S. Raymond
2001-04-20 18:50                           ` Russell King
2001-04-20 21:23                             ` Andreas Dilger
2001-04-21  0:52                               ` Proposal for better attribution structure Eric S. Raymond
2001-04-20  8:19       ` OK, let's try cleaning up another nit. Is anyone paying attention? David Woodhouse
2001-04-20 19:47     ` Eric S. Raymond
2001-04-20 20:00       ` Matthew Wilcox
2001-04-20 20:13         ` Eric S. Raymond
2001-04-20 20:55       ` Alan Cox
2001-04-21  6:48       ` [parisc-linux] " Grant Grundler
2001-04-21 14:52         ` Eric S. Raymond
2001-04-20 13:08   ` Alan Cox
2001-04-20 13:18     ` Eric S. Raymond
2001-07-29 10:47     ` Riley Williams

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=20010420200859.B5510@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=acahalan@cs.uml.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=esr@thyrsus.com \
    --cc=james.rich@m.cc.utah.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=parisc-linux@parisc-linux.org \
    --cc=trini@kernel.crashing.org \
    --cc=willy@ldl.fc.hp.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