MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 8BIT
Message-id: <1391646482.25542.72.camel@kjgkr>
Subject: Re: linux-next: bad commits in the f2fs tree
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Reply-to: jaegeuk.kim@samsung.com
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Date: Thu, 06 Feb 2014 09:28:02 +0900
In-reply-to: <20140206110401.7888b06cbd651b842404b902@canb.auug.org.au>
References: <20140206110401.7888b06cbd651b842404b902@canb.auug.org.au>
Organization: Samsung
DLP-Filter: Pass
Sender: linux-kernel-owner@vger.kernel.org

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/