[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130410002311.8a0b0503bcbda151b9de9469@canb.auug.org.au>
Date: Wed, 10 Apr 2013 00:23:11 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: sedat.dilek@...il.com
Cc: linux-next <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Apr 9
Hi Sedat,
On Tue, 9 Apr 2013 16:11:50 +0200 Sedat Dilek <sedat.dilek@...il.com> wrote:
>
> [ CC Al Viro ]
You forgot to do that ...
> Is there a "magic" git-command to revert all commits coming from your
> latest vfs-merge (commit c1c04d3667608a630ae0821995b465a523e83fb1)?
>
> 2013-04-09 11:36 Stephen Rothwell │ M─┐ │ │ │ │ │ │ │ 20130405/vfs
You would normally do "git revert -m 1 c1c04d366760". However, that does
not revert cleanly in today's linux-next (due to more patches modifying
the files involved).
> After reverting all these commits I would like to pull-in latest
> vfs.git#for-next.
It would probably be easier to wait for tomorrow's linux-next. Or just
test Al's tree in its own.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists