From: Andi Kleen <andi@firstfloor.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ray Lee <ray-lk@madrabbit.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
torvalds@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: Please pull ACPI updates
Date: Thu, 17 Jul 2008 22:34:18 +0200 [thread overview]
Message-ID: <487FACCA.5040304@firstfloor.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0807171304220.2959@woody.linux-foundation.org>
>
> It means that a person who ran my tree as of yesterday,
Ok I understand this applies to your tree because you have lots of direct users.
And also people tend to only submit patches to you which are relatively
well tested already and don't really do "raw development" in your tree.
But for people lower down the food chain that's not necessarily the
case. They usually only get some testing through -mm/linux-next
and perhaps occasionally for individual patches posted to verify
bugs. They tend to not have many people directly pulling their stuff
(and if it's someone it is some downstream developer who typically can deal
with an occasional rebase)
Anyways if you prefer I can send to you the raw development history
(with all reverts, fixups, non bisectable section etc.), but I suspect
you wouldn't really be very happy with that.
-Andi
next prev parent reply other threads:[~2008-07-17 20:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 21:45 Please pull ACPI updates Andi Kleen
2008-07-16 22:11 ` Rafael J. Wysocki
2008-07-16 23:33 ` Jesse Barnes
2008-07-16 23:45 ` Linus Torvalds
2008-07-16 23:51 ` Jesse Barnes
2008-07-17 0:32 ` Linus Torvalds
2008-07-17 0:53 ` Linus Torvalds
2008-07-17 2:26 ` Jesse Barnes
2008-07-17 2:56 ` Linus Torvalds
2008-07-17 6:45 ` Andi Kleen
2008-07-17 15:06 ` Linus Torvalds
2008-07-17 6:40 ` Andi Kleen
2008-07-17 15:03 ` Linus Torvalds
2008-07-17 18:49 ` Len Brown
2008-07-17 19:12 ` Harvey Harrison
2008-07-17 19:50 ` Andi Kleen
2008-07-17 19:12 ` Linus Torvalds
2008-07-17 19:16 ` Linus Torvalds
2008-07-17 21:15 ` J. Bruce Fields
2008-07-17 23:11 ` [PATCH] Revert duplicate "dock: bay: Don't call acpi_walk_namespace() when ACPI is disabled" commit (was: Please pull ACPI updates) Thomas Gleixner
2008-07-17 23:25 ` [PATCH] Revert duplicate "dock: bay: Don't call acpi_walk_namespace() when ACPI is disabled" commit Andi Kleen
2008-07-18 0:07 ` [PATCH] Revert duplicate "ACPI: don't walk tables if ACPI was disabled" commit (was: Please pull ACPI updates) Thomas Gleixner
2008-07-17 6:47 ` Please pull ACPI updates Andi Kleen
2008-07-17 15:18 ` Linus Torvalds
2008-07-17 15:47 ` Linus Torvalds
2008-07-17 16:02 ` Linus Torvalds
2008-07-17 16:23 ` Andi Kleen
2008-07-17 19:11 ` Ray Lee
2008-07-17 19:49 ` Andi Kleen
2008-07-17 20:01 ` Linus Torvalds
2008-07-17 20:14 ` Andi Kleen
2008-07-17 20:16 ` Linus Torvalds
2008-07-17 20:28 ` Linus Torvalds
2008-07-18 13:25 ` Olivier Galibert
2008-07-18 15:57 ` Ray Lee
2008-07-17 20:34 ` Andi Kleen [this message]
2008-07-17 20:11 ` Ray Lee
2008-07-17 20:29 ` Andi Kleen
2008-07-18 6:39 ` david
-- strict thread matches above, loose matches on Subject: below --
2008-07-24 20:36 Andi Kleen
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=487FACCA.5040304@firstfloor.org \
--to=andi@firstfloor.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.org \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--cc=torvalds@linuxfoundation.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