From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [git pull] vfs.git regression fix
Date: Mon, 18 Jan 2016 09:49:11 +0200 [thread overview]
Message-ID: <569C98F7.9010405@ti.com> (raw)
In-Reply-To: <20160116134458.GK17997@ZenIV.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On 16/01/16 15:44, Al Viro wrote:
> FWIW, the main inconvenience with git request-pull is that it still needs
> s/gitolite@ra.kernel.org:/git:\/\/git.kernel.org/ postprocessing. It mimics
> the git push, but the remote you are pushing to probably won't be usable for
> pulling by others. Looks like it would be useful to have something like
> pull_url = git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
> to go with
> url = gitolite@ra.kernel.org:/pub/scm/linux/kernel/git/viro/vfs.git
> in .git/config, settable by something in git remote. OTOH, it's possible to
> emulate by setting an extra remote and using git push vfs <...> for pushes,
> while doing git request-pull origin vfs-pull <...> for pull requests...
Isn't "pushurl" for that? I have:
[remote "origin"]
url = git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git
pushurl = gitolite.kernel.org:/pub/scm/linux/kernel/git/tomba/linux.git
fetch = +refs/heads/*:refs/remotes/origin/*
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-01-18 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 20:18 [git pull] vfs.git regression fix Al Viro
2016-01-15 20:41 ` Linus Torvalds
2016-01-15 21:00 ` Al Viro
2016-01-15 21:08 ` Linus Torvalds
2016-01-16 13:44 ` Al Viro
2016-01-16 19:05 ` Linus Torvalds
2016-01-18 7:49 ` Tomi Valkeinen [this message]
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=569C98F7.9010405@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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).