[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [parisc-linux] Re: Version 0.9 of PA-RISC Linux Released

On Tue, 05 Jun 2001, Matthew Wilcox wrote:

> I've been working on this
> project for more than 2 years now, working for 3 different companies
> during that time.  

I'll be glad to match my 4 decades of experience against your 2 years anytime.
> Not the way it works. 
> Send patches now and they'll (probably) get integrated.

Perhaps that is not how it works in your world, but consider -

The only way to validate a change as a potential patch is:

1) start with a clean (error and warning free) build that
boots and runs on the machine of interest.

2) hack, change, modify, whatever

3) when done, make another clean build that boots and runs
on the machine of interest.

4) evaluate the effects of the change(s).

5) If successful - then you MIGHT have something worth
submitting as a POTENTIAL patch.

Exactly the same 5 steps your developers take before they
commit a change to CVS.

> So far i've heard nothing but talk from you.  

That's right - until it is a clean build, boots and runs -
everything is talk and speculation.

>  Things will move on and you'll get left behind.

So what?

The only changes I make outside of the parisc specific
branch of the source tree are to bring the code in line
with 2.4.4 (stable).

The changes I make inside of the parisc specific branch
of the tree will be (someday) found by your own developers.

Just a matter of do you want to duplicate the time and 
trouble of finding them yourself, or read about them in
the mail archives.

If you are serious about my suggestions being counter-productive,
I will gladly spend the time I am taking to write them for other purposes.


Reply to: