From: Olivier Galibert <galibert@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>, 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: Fri, 18 Jul 2008 15:25:21 +0200 [thread overview]
Message-ID: <20080718132521.GA94799@dspnet.fr.eu.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0807171323320.2959@woody.linux-foundation.org>
On Thu, Jul 17, 2008 at 01:28:20PM -0700, Linus Torvalds wrote:
> One final note on this: the above is obviously not a problem for simple
> code that only really does one thing, and in particular for code that you
> wrote yourself. Moving your own commits around to make them make more
> sense - or splitting them up etc - is often a _good_ thing, even if it
> obviously does change history.
You seem to be talking of subtly different things Andi and you, and
since I'm quite interested in the answer I'll try to rephrase what I
understood.
You say "don't rebase on the most recent kernel version". Andi seems
to accept that going forwards. You say "use topic branches that are
based on whatever kernel version you had at the time, I'll do the
merge". That's ok too. His remaining question is "what do I do with
broken patches _in_the_topic_branch_?". He wants to
amend/merge/split/reorder within the topic branch so that the branch
itself is bisectable. So what should be done there?
OG.
next prev parent reply other threads:[~2008-07-18 13:25 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
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 [this message]
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=20080718132521.GA94799@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=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
all inboxes | Powered by JetHome®