From: Stephen Rothwell <sfr@canb.auug.org.au>
To: jaegeuk.kim@samsung.com
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: bad commits in the f2fs tree
Date: Thu, 6 Feb 2014 11:38:45 +1100 [thread overview]
Message-ID: <20140206113845.081b6847d8263f2fd37adefd@canb.auug.org.au> (raw)
In-Reply-To: <1391646482.25542.72.camel@kjgkr>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
Hi Jaegeuk,
On Thu, 06 Feb 2014 09:28:02 +0900 Jaegeuk Kim <jaegeuk.kim@samsung.com> 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 sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-02-06 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 0:04 Stephen Rothwell
2014-02-06 0:28 ` Jaegeuk Kim
2014-02-06 0:38 ` Stephen Rothwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140206113845.081b6847d8263f2fd37adefd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®