Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: sedat.dilek@gmail.com
Cc: linux-next <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 9
Date: Wed, 10 Apr 2013 00:23:11 +1000
Message-ID: <20130410002311.8a0b0503bcbda151b9de9469@canb.auug.org.au> (raw)
In-Reply-To: <CA+icZUVk-iLtodZi_46qmk410Ei+tW6RR5kV2fx0N8v6neKTPQ@mail.gmail.com>


[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

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).

> 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@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply index

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 10:56 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 [this message]
2013-04-09 14:32       ` Sedat Dilek
2013-04-09 15:11         ` Sedat Dilek
2013-04-09 15:48           ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
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=20130410002311.8a0b0503bcbda151b9de9469@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    /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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git