From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 9
Date: Tue, 9 Apr 2013 16:32:13 +0200 [thread overview]
Message-ID: <CA+icZUUboWkL8vHvN6+xk=9kz8SXexxgMN-g+xuPB24T1wTSRw@mail.gmail.com> (raw)
In-Reply-To: <20130410002311.8a0b0503bcbda151b9de9469@canb.auug.org.au>
On Tue, Apr 9, 2013 at 4:23 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Sedat,
>
> On Tue, 9 Apr 2013 16:11:50 +0200 Sedat Dilek <sedat.dilek@gmail.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).
>
Just wanted to improve my git Know-How.
>> 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.
Doug reported problems on his way "reverting the current vfs stuff"
and Al's new tree was reported as OK.
A lot of merge-conflicts... that's what I see when trying to pull in
Al's tree in today's Linux-Next.
So, I better wait for tommorrow.
Anyway, a warning in your CHANGELOG is very much appreciated on such
KNOWN ISSUES.
Regards,
- Sedat -
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
next prev parent reply other threads:[~2013-04-09 14:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 10:56 linux-next: Tree for Apr 9 Sedat Dilek
2013-04-09 12:37 ` Sedat Dilek
2013-04-09 13:34 ` Sedat Dilek
2013-04-09 13:59 ` Stephen Rothwell
2013-04-09 14:03 ` Sedat Dilek
2013-04-09 14:11 ` Sedat Dilek
2013-04-09 14:23 ` Stephen Rothwell
2013-04-09 14:32 ` Sedat Dilek [this message]
2013-04-09 15:11 ` Sedat Dilek
2013-04-09 15:48 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2024-04-09 4:50 Stephen Rothwell
2021-04-09 11:51 Stephen Rothwell
2020-04-09 5:10 Stephen Rothwell
2019-04-09 8:00 Stephen Rothwell
2019-04-09 18:25 ` Guenter Roeck
2019-04-09 18:44 ` Trond Myklebust
2018-04-09 4:42 Stephen Rothwell
2015-04-09 9:31 Stephen Rothwell
2014-04-09 7:22 Stephen Rothwell
2013-04-09 9:30 Stephen Rothwell
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='CA+icZUUboWkL8vHvN6+xk=9kz8SXexxgMN-g+xuPB24T1wTSRw@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).