From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: Please pull ACPI updates
Date: Wed, 16 Jul 2008 17:32:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807161728560.2835@woody.linux-foundation.org> (raw)
In-Reply-To: <200807161651.44990.jbarnes@virtuousgeek.org>
On Wed, 16 Jul 2008, Jesse Barnes wrote:
> >
> > Andi did not. The whole series I pulled was rebased today at 2PM.
>
> Ugg, when Andi took over we talked about it; I thought we had agreed that he
> would stick with Len's tree. I guess I was wrong.
Well, I haven't actually seen Len's original tree, so maybe the stuff Andi
pushed was just the stuff he had queued up independently. I guess I
shouldn't judge before I'm sure.
> Is a topic branch flow like what Len uses documented somewhere that you know
> of? I know my process could use some improvement; I'd rather not have to
> wait for Len to come back to ask him. :)
Len wrote it up at one point, but I can't for the life of me remember
where.
He's not the onyl one to ask, though - Ingo and Thomas seem to have picked
up topic branches pretty well (I had some issues with a couple of the
topics, but they weren't fundamental and the major one was probably
because Ingo tried a bit too hard to make sure that I never saw any
conflicts at all).
Other topic branch users include Jeff Garzik and rmk. There's definitely
people around who should be able to talk about what they are doing.
Linus
next prev parent reply other threads:[~2008-07-17 0:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 21:45 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 [this message]
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
2008-07-17 20:11 ` Ray Lee
2008-07-17 20:29 ` Andi Kleen
2008-07-18 6:39 ` david
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=alpine.LFD.1.10.0807161728560.2835@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®