From: Simon Arlott <simon@fire.lp0.eu>
To: Olaf Hering <olaf@aepfle.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org
Subject: Re: Revert "[POWERPC] <various>"
Date: Mon, 30 Apr 2007 20:56:05 +0100 [thread overview]
Message-ID: <463649D5.9000406@simon.arlott.org.uk> (raw)
In-Reply-To: <20070430194911.GA1156@aepfle.de>
On 30/04/07 20:49, Olaf Hering wrote:
> 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.
The reverts themselves are not the real problem, a git bisect could occur
between the commit adding it and the one that reverts it. If that commit
introduced a bug then surely it would be better to avoid releasing it
elsewhere even if it will be reverted in the same batch.
Of course, this is probably difficult to do with git and impossible if
someone has cloned the bad commit already and tries to pull :/
Is it possible to mass copy all the good commits to create a clean branch?
--
Simon Arlott
next prev parent reply other threads:[~2007-04-30 19:56 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
2007-04-30 19:56 ` Simon Arlott [this message]
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=463649D5.9000406@simon.arlott.org.uk \
--to=simon@fire.lp0.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olaf@aepfle.de \
/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