Re: Why is the new patch against 2.4.20-pre3 and not 2.4.1 9?

On Wed, Aug 21, 2002 at 12:58:17PM +0200, VALETTE Eric wrote:

Arndt Schoenewald wrote:

quoted

It seems that Andrew's merge with 2.4.10-pre3 instead of 2.4.19 was an
accident rather than a deliberate decision. When he announced the new
ACPI source release on on Fri, 16 Aug 2002, he wrote:

   [snip]
   Second, the Linux 2.5 patch is up on sf.net/projects/acpi, and
   includes the changes listed below. Unfortunately, due to a BK error
   on my part (I merged the ACPI patch onto the tip of the 2.4 BK tree,
   instead of 2.4.19) the 2.4 patch is going to have to wait until
   Marcelo releases 2.4.20-pre3.
   [snip]

So please don't get upset too much; mistakes like this can happen.

So why did he release a second patch for pre4 after that then and not 
2.4.19??? Will he be releasing new patch for each preX?

Someone on this list asked him to release a 2.4.20-pre4 patch because of
known problems with 2.4.20-pre3. This was an exceptional case; I don't
think he is going to release more of these -preX patches. The reason for
not releasing a 2.4.19 patch seems to be that the backport for 2.4.19
would take time that he does not want to invest. You or everybody else
on this list is welcome to step in and do this work for the benefit of
all of us.

I understand using BK tree for things that will be included and 
avoid/simplify merging for official maintainer. As far as I understand 
Marcello is not going to integrate ACPI in 2.4.20...

Don't know about that. My hope was that it will go into 2.4.20.

Arndt


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390