From: Jeff Garzik <jgarzik-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Linus Torvalds <torvalds-3NddpPZAyC0@public.gmane.org>,
Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [BK PATCH] ACPI 20030918
Date: Wed, 01 Oct 2003 13:14:46 -0400 [thread overview]
Message-ID: <3F7B0B86.70206@pobox.com> (raw)
In-Reply-To: <1064986198.2574.190.camel-D2Zvc0uNKG8@public.gmane.org>
Len Brown wrote:
> Hi Linus, please do a
>
> bk pull http://linux-acpi.bkbits.net/linux-acpi-release-2.6.0
>
> With this batch, 2.6 includes all the ACPI updates in 2.4.
Looks good, but one comment for the future:
> <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> (03/09/30 1.1381)
> [ACPI] acpi4asus-0.25-0.26.diff (Karol Kozimor)
>
> <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> (03/09/30 1.1380)
> [ACPI] acpi4asus-0.24a-0.25-2.6.0-test (Karol Kozimor)
>
All the comments were quite descriptive except for these... a filename
doesn't me much about the content of the patch.
Jeff
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-10-01 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0D56318@hdsmsx402.hd.intel.com>
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0D56318-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-10-01 5:29 ` [BK PATCH] ACPI 20030918 Len Brown
[not found] ` <1064986198.2574.190.camel-D2Zvc0uNKG8@public.gmane.org>
2003-10-01 5:46 ` [BK PATCH] 2.4.23 " Len Brown
2003-10-01 17:14 ` Jeff Garzik [this message]
[not found] ` <3F7B0B86.70206-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2003-10-01 22:56 ` [ACPI] Re: [BK PATCH] " Karol Kozimor
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=3F7B0B86.70206@pobox.com \
--to=jgarzik-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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