From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [git pull] more vfs.git stuff
Date: Fri, 22 Jan 2016 18:42:00 +0000 [thread overview]
Message-ID: <20160122184200.GC17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFxRXUraKUHX98adn1X8gRt1oRU5CxKpvyHEiSW+9dyC9g@mail.gmail.com>
On Fri, Jan 22, 2016 at 10:26:18AM -0800, Linus Torvalds wrote:
> On Thu, Jan 21, 2016 at 3:04 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > [trying to use git request-pull; result looks more or less sane, AFAICT...]
>
> Looks fine, if you can just fix this part:
>
> > gitolite@ra.kernel.org:/pub/scm/linux/kernel/git/viro/vfs.git for-linus
>
> and have it point to the public git://git.kernel.org/.. thing.
>
> Either by just using "pushurl" for origin, or by having separate
> push/pull names entirely.
Sorry about that - pushurl added, both git push and git request-pull seem
to be working now.
BTW, looks like ext4 is the only pending i_mutex-sensitive tree; once
it's pulled, I'll regenerate the inode_{lock,unlock,trylock,...} patch
and send it your way.
next prev parent reply other threads:[~2016-01-22 18:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 23:04 [git pull] more vfs.git stuff Al Viro
2016-01-22 18:26 ` Linus Torvalds
2016-01-22 18:42 ` Al Viro [this message]
2016-01-22 18:45 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2013-07-14 17:34 Al Viro
2013-05-09 19:26 Al Viro
2013-05-09 20:12 ` Linus Torvalds
2013-05-09 20:21 ` Linus Torvalds
2013-05-09 20:28 ` Al Viro
2013-05-09 20:34 ` Al Viro
2013-05-09 20:46 ` Linus Torvalds
2013-05-07 19:17 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=20160122184200.GC17997@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 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).