linux-kernel - Re: linux-next: rebase of the drivers-x86 tree

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: <20130715191708.GA514@srcf.ucam.org>
Date:	Mon, 15 Jul 2013 20:17:08 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: rebase of the drivers-x86 tree

On Mon, Jul 15, 2013 at 10:13:06AM +1000, Stephen Rothwell wrote:

> That is hardly a reason to rebase your tree.  Just add another commit to
> correct the situation.  The tree as it stood would not have affected
> anyone's building, running or bisecting.

I verified that the only difference before and after rebasing was that 
the file permission was back the way it should be. Why clutter history?

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/