From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Linus Torvalds <torvalds-3NddpPZAyC0@public.gmane.org>,
Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PATCH] ACPI patches for 2.6.13
Date: Sat, 30 Jul 2005 11:58:35 +0200 [thread overview]
Message-ID: <20050730095834.GA1942@elf.ucw.cz> (raw)
In-Reply-To: <1122702560.26850.9.camel@toshiba>
Hi!
> Please pull from:
>
> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/lenb/to-linus/
>
> Sorry to be scrambling so late in the 2.6.13 release cycle --
> we'll do better with 2.6.14.
>
> thanks,
> -Len
>
> p.s.
> Latest ACPI plain patch, including stuff waiting for 2.6.14 is available
> here:
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.12/
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.12/broken-out/
What happened to those cleanups I sent to you in Ottawa? I never
received any reply, can't see them below, and can't see them in
broken-out either (maybe I'm looking wrong way?).
Pavel
--
teflon -- maybe it is a trademark, but it should not be.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-30 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d120d50005071312322b5d4bff@mail.gmail.com>
[not found] ` <1121286258.4435.98.camel@mindpipe>
[not found] ` <20050713134857.354e697c.akpm@osdl.org>
[not found] ` <20050713211650.GA12127@taniwha.stupidest.org>
[not found] ` <Pine.LNX.4.63.0507131639130.13193@twinlark.arctic.org>
[not found] ` <20050714005106.GA16085@taniwha.stupidest.org>
[not found] ` <Pine.LNX.4.63.0507131810430.13193@twinlark.arctic.org>
[not found] ` <1121304825.4435.126.camel@mindpipe>
[not found] ` <Pine.LNX.4.58.0507131847000.17536@g5.osdl.org>
[not found] ` <1121326938.3967.12.camel@laptopd505.fenrus.org>
[not found] ` <20050714121340.GA1072@ucw.cz>
[not found] ` <Pine.LNX.4.58.0507140933150.19183@g5.osdl.org>
[not found] ` <1121383050.4535.73.camel@mindpipe>
[not found] ` <Pine.LNX.4.58.0507141623490.19183@g5.osdl.org>
[not found] ` <1121384499.4535.82.camel@mindpipe>
[not found] ` <Pine.LNX.4.58.0507141648070.19183@g5.osdl.org>
[not found] ` <Pine.LNX.4.58.0507141648070.19183-hNm40g4Ew95AfugRpC6u6w@public.gmane.org>
2005-07-30 5:49 ` [GIT PATCH] ACPI patches for 2.6.13 Len Brown
2005-07-30 9:58 ` Pavel Machek [this message]
2005-08-03 23:16 ` [GIT PATCH] ACPI patches for 2.6.13-rc5 Len Brown
2005-08-04 17:11 ` [GIT PATCH] ACPI patches for 2.6.13-rc5+ Len Brown
2005-08-15 20:35 ` [GIT PATCH] ACPI patch for 2.6.13-rc6 Len Brown
2005-07-31 6:12 [GIT PATCH] ACPI patches for 2.6.13 Brown, Len
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=20050730095834.GA1942@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-3NddpPZAyC0@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