Linux PARISC architecture development
 help / color / mirror / Atom feed
From: willy@ldl.fc.hp.com (Matthew Wilcox)
To: "Eric S. Raymond" <esr@thyrsus.com>,
	Matthew Wilcox <willy@ldl.fc.hp.com>,
	linux-kernel@vger.kernel.org, parisc-linux@parisc-linux.org
Subject: [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention?
Date: Thu, 19 Apr 2001 21:17:49 -0600	[thread overview]
Message-ID: <20010419211749.I4217@zumpano.fc.hp.com> (raw)
In-Reply-To: <20010419230009.A32500@thyrsus.com>; from esr@thyrsus.com on Thu, Apr 19, 2001 at 11:00:09PM -0400

On Thu, Apr 19, 2001 at 11:00:09PM -0400, Eric S. Raymond wrote:
> What is the right procedure for doing changes like this?  Is "don't
> touch that tree" a permanent condition, or am I going to get a chance
> to clean up the global CONFIG_ namespace after your next merge-down?

Our current status is that we've got a patch with Alan that's been sitting
in his tree for a while (things got trickier than he expected and he
hasn't been able to merge that upstream to Linus yet).  Meanwhile we've
carried on development as normal.  So even after the patches in Alan's
tree land, we've still got a fair hunk of changes to go in.

My preference would be for you to fetch our tree 

cvs -d :pserver:anonymous@puffin.external.hp.com:/home/cvs/parisc login
[no password]

cvs -d :pserver:anonymous@puffin.external.hp.com:/home/cvs/parisc co linux

and submit patches to us, which will get to Linus in the fullness of time.
I'm aware this might not be terribly satisfactory for you, but we're
doing our best not to lose our way amid the churn of development right
now and having patches which haven't followed a progression through
us makes that significantly harder.

> Could I ask you to audit your tree and change the prefix on any 
> CONFIG_ symbols that are private over there?  This would make life 
> easier for my auditing tools (kxref and Stephen Cole's ach script).

I don't think we have any of those.  We certainly have symbols which are
defined for symmetry and may not actually be used yet (CONFIG_PA11 might not
be, perhaps).  But that's what happens when you're developing software :-)

  reply	other threads:[~2001-04-20  3:17 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20  2:36 [parisc-linux] Re: 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 [this message]
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           ` 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
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 21:39                                           ` David Woodhouse
2001-04-21  0:24                                             ` Eric S. Raymond
2001-04-20 22:53                                           ` Alan Cox
2001-04-21  0:37                                             ` Eric S. Raymond
2001-04-21 12:32                                               ` David Woodhouse
2001-04-21 23:39                                               ` Jes Sorensen
2001-04-20 18:50                           ` Russell King
2001-04-20 21:23                             ` Andreas Dilger
2001-04-21  0:52                               ` [parisc-linux] Proposal for better attribution structure Eric S. Raymond
2001-04-20  8:19       ` [parisc-linux] Re: 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       ` 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

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=20010419211749.I4217@zumpano.fc.hp.com \
    --to=willy@ldl.fc.hp.com \
    --cc=esr@thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parisc-linux@parisc-linux.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