linux-kernel - Re: linux-next: bad commits in the f2fs 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] [thread-next>] [day] [month] [year] [list]

Message-id: <1391646482.25542.72.camel@kjgkr>
Date:	Thu, 06 Feb 2014 09:28:02 +0900
From:	Jaegeuk Kim <jaegeuk.kim@...sung.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: bad commits in the f2fs tree

Hi Stephen,

2014-02-06 (목), 11:04 +1100, Stephen Rothwell:
> Hi Jaegeuk,
> 
> Looking at the f2fs tree today, it has *copies* of several commits that
> are in Linus' tree (including b522196a6ffb "Linus 3.14-rc1" which is
> commit 38dbfb59d117 in Linus' tree).  I assume this happened when you
> tried to rewrite your tree. :-(

I fixed that.
Sorry for the mistake. :)

> 
> I can't use that tree, so will use the version of f2fs from next-20140105.

-- 
Jaegeuk Kim
Samsung

--
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/