linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: linuxppc-dev@ozlabs.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Revert "[POWERPC] <various>"
Date: Mon, 30 Apr 2007 21:49:11 +0200	[thread overview]
Message-ID: <20070430194911.GA1156@aepfle.de> (raw)
In-Reply-To: <46362B14.6090106@simon.arlott.org.uk>

On Mon, Apr 30, Simon Arlott wrote:

> There are a few powerpc patches plus reverts in the recent push to 
> torvalds/linux-2.6 - shouldn't this be avoided whenever possible because it 
> could cause problems for people trying to use git bisect?

The reverts do not cause compile failures (I hope).
You may lose IDE if you happen to debug something on Pegasos.
I'm sure the real bisect breakers are elsewhere.

  reply	other threads:[~2007-04-30 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 17:44 Revert "[POWERPC] <various>" Simon Arlott
2007-04-30 19:49 ` Olaf Hering [this message]
2007-04-30 19:56   ` Simon Arlott
2007-05-01  0:58     ` Stephen Rothwell

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=20070430194911.GA1156@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=simon@fire.lp0.eu \
    /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;
as well as URLs for NNTP newsgroup(s).