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 11:38:54 +0200	[thread overview]
Message-ID: <20020821093854.GA14643@digda.intern.quelltext.com> (raw)
In-Reply-To: <3D634335.40207-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.org>

Hi Eric!

On Wed, Aug 21, 2002 at 09:37:25AM +0200, VALETTE Eric wrote:
> Grover, Andrew wrote:
> >>From: VALETTE Eric [mailto:valette-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.org] 
> >>I've tried to apply it on 2.4.19, it fails. I've tried on 
> >>2.4.20-pre4 it also fails :-(. So I have to stick with 2.4.20-pre3
> >>which is known to cause some hangup on boot (see Marcello comment
> >>for pre4).
> >>
> >>Can we have some light of why 20-pre3 instead of 19? Or is it just 
> >>cahotic because of the temperature and beverage?
> >
> >Because that's what I originally merged against, and I didn't want to
> >remerge against .19.
> 
> That is rather not a sound answer. Why did you choose to merge with 
> 2.4.10-pre3 instead of 2.4.19? I apply other patches to kernel that may 
> well conflict with other pre series and I'm not alone. Most of *normal* 
> people make patches only for official stable kernels (e.g ntfs, kdbg, 
> packet writing for UDF). Again I think this is just a lack of methodlogy 
>  (like non usage of acessible bug tracking system...).

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.

Best regards,
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  9:38 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 [this message]
2002-08-21 10:58       ` VALETTE Eric
     [not found]         ` <3D637249.9060904-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.org>
2002-08-21 12:35           ` Arndt Schoenewald
  -- 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=20020821093854.GA14643@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