From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs and fs patches for 3.1, part 1
Date: Sat, 23 Jul 2011 02:27:12 +0100 [thread overview]
Message-ID: <20110723012712.GG31405@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFxwyCS+G5g-EdL48TPd7saU+3wCWPf3EBoY7Amf+tb7Qw@mail.gmail.com>
On Fri, Jul 22, 2011 at 05:54:15PM -0700, Linus Torvalds wrote:
> *Most*, but not all, of the commits you list seem to exist in the
> for-next branch.
The rest is a build fix from Randy + obvious ERR_CAST-instead-of-cast +
isofs lock removal + a couple of IN_DELETE_SELF fixes that should've gone
in last cycle...
> Which is identical to the "untested" branch, so that, together with
> the "not everything listed in your shortlog is there" makes me not get
> the warm and fuzzies.
#untested == #master in my local tree, no more than that... My apologies
about the forgotten push.
next prev parent reply other threads:[~2011-07-23 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 0:01 [git pull] vfs and fs patches for 3.1, part 1 Al Viro
2011-07-23 0:48 ` Linus Torvalds
2011-07-23 0:54 ` Linus Torvalds
2011-07-23 1:27 ` Al Viro [this message]
2011-07-23 1:21 ` Al Viro
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=20110723012712.GG31405@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.