public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arndt Schoenewald <abs-SA7OhAOe25xnNxvc45mVi0K323yFvGpRdefyYXQ/eNw@public.gmane.org>
To: VALETTE Eric <valette-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Why is the new patch against 2.4.20-pre3 and not 2.4.1 9?
Date: Wed, 21 Aug 2002 14:35:22 +0200	[thread overview]
Message-ID: <20020821123522.GA17263@digda.intern.quelltext.com> (raw)
In-Reply-To: <3D637249.9060904-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.org>

On Wed, Aug 21, 2002 at 12:58:17PM +0200, VALETTE Eric wrote:
> Arndt Schoenewald wrote:
> 
> >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

  parent reply	other threads:[~2002-08-21 12:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20 17:42 Why is the new patch against 2.4.20-pre3 and not 2.4.1 9? Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD0236DDB1-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-08-21  1:58   ` KOCHI, Takayoshi
2002-08-21  7:37 ` VALETTE Eric
     [not found]   ` <3D634335.40207-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.org>
2002-08-21  8:15     ` Charl P. Botha
2002-08-21  9:38     ` Arndt Schoenewald
2002-08-21 10:58       ` VALETTE Eric
     [not found]         ` <3D637249.9060904-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.org>
2002-08-21 12:35           ` Arndt Schoenewald [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-21 16:36 Grover, Andrew
2002-08-21 17:30 Grover, Andrew

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=20020821123522.GA17263@digda.intern.quelltext.com \
    --to=abs-sa7ohaoe25xnnxvc45mvi0k323yfvgprdefyyxq/enw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=valette-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.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