2014-02-06 00:04:13

by Stephen Rothwell

[permalink] [raw]
Subject: linux-next: bad commits in the f2fs tree

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 can't use that tree, so will use the version of f2fs from next-20140105.
--
Cheers,
Stephen Rothwell [email protected]


Attachments:
(No filename) (401.00 B)
(No filename) (836.00 B)
Download all attachments

2014-02-06 00:29:34

by Jaegeuk Kim

[permalink] [raw]
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

2014-02-06 00:39:03

by Stephen Rothwell

[permalink] [raw]
Subject: Re: linux-next: bad commits in the f2fs tree

Hi Jaegeuk,

On Thu, 06 Feb 2014 09:28:02 +0900 Jaegeuk Kim <[email protected]> wrote:
>
> 2014-02-06 (목), 11:04 +1100, Stephen Rothwell:
> >
> > 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.

I have refetched your tree and will use it today.

--
Cheers,
Stephen Rothwell [email protected]


Attachments:
(No filename) (550.00 B)
(No filename) (836.00 B)
Download all attachments