linux-kernel - Re: linux-next: bad commit in the luto-misc 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20150105104857.1abcec86@canb.auug.org.au>
Date:	Mon, 5 Jan 2015 10:48:57 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: linux-next: bad commit in the luto-misc tree

Hi Andy,

On Sun, 4 Jan 2015 15:42:31 -0800 Andy Lutomirski <luto@...capital.net> wrote:
>
> Sorry.  I totally failed here.  I swear I rebased onto the latest RCU
> tree, double-checked it, and pushed that exact revision to luto/next.
> Somehow I pushed a much older development commit.  I have no idea how
> I did that.  I didn't even know I still had that commit around at all.

OK, I have refetched your tree for today and it looks fine.

> Fixed now, I think.  Next time I will push to luto/next and
> double-check that I pushed the commit I thought I pushed.

Thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped