linux-kernel - Re: Revert "[POWERPC] <various>"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070501105805.a27984d8.sfr@canb.auug.org.au>
Date:	Tue, 1 May 2007 10:58:05 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Simon Arlott <simon@...e.lp0.eu>
Cc:	Olaf Hering <olaf@...fle.de>, linuxppc-dev@...abs.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Revert "[POWERPC] <various>"

On Mon, 30 Apr 2007 20:56:05 +0100 Simon Arlott <simon@...e.lp0.eu> wrote:
>
> 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.

At least one of the reverts was just because the original commit clashed
with a commit in a different tree (netdev) so that will not cause and
build or runtime problems.

> Of course, this is probably difficult to do with git and impossible if
> someone has cloned the bad commit already and tries to pull :/

Not impossible, but it rebases the tree which means that people who have
pulled the tree need to force their next updates.

> Is it possible to mass copy all the good commits to create a clean branch?

It is, but in this case was probably not worth it.

--
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped