public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "VALETTE Eric" <valette-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.org>
To: Arndt Schoenewald
	<abs-SA7OhAOe25xnNxvc45mVi0K323yFvGpRdefyYXQ/eNw@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 12:58:17 +0200	[thread overview]
Message-ID: <3D637249.9060904@crf.canon.fr> (raw)
In-Reply-To: 20020821093854.GA14643@digda.intern.quelltext.com

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?

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...


-- 
    __
   /  `                          Eric Valette - Canon CRF
  /--   __  o _.                 Product Dev. Group Software Team Leader
(___, / (_(_(__                 Rue de la touche lambert
                                 35517 Cesson-Sevigne  Cedex
                                 FRANCE
Tel: +33 (0)2 99 87 68 91       Fax: +33 (0)2 99 84 11 30
E-mail: valette-9L3uxOwa2HHHNWWW6QW1Ag@public.gmane.org    http://www.crf.canon.fr



-------------------------------------------------------
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

  reply	other threads:[~2002-08-21 10:58 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 [this message]
     [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=3D637249.9060904@crf.canon.fr \
    --to=valette-9l3uxowa2hhhnwww6qw1ag@public.gmane.org \
    --cc=abs-SA7OhAOe25xnNxvc45mVi0K323yFvGpRdefyYXQ/eNw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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