From: Paul Sokolovsky <paul.sokolovsky@linaro.org>
To: git@vger.kernel.org
Subject: url.<base>.insteadOf used for server-side redirection?
Date: Wed, 9 Mar 2016 16:33:36 +0700 [thread overview]
Message-ID: <20160309163336.42161c01@x230> (raw)
Hello,
There's a nice git config directive url.insteadOf
(https://www.kernel.org/pub/software/scm/git/docs/git-config.html ,
search for "insteadOf"). However, than man doesn't make it explicit if
it can be used in server-side repository config, and all examples on
the net appear to be about its usage on user's local side.
So, is the remote use supported? Like a user issues a git clone with one
URL, but gets redirect to another URL and git client proceeds to clone
from it. Our usecase is to redirect git:// clones to http:// to
avoid some scalability issues.
If it's not supported, any chance it could be? Maybe it was discussed
and voted down? Or voted up and someone has it in their queue? Note
that the talk is about git-specific redirects, like redirecting one git
protocol to another.
Thanks,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
reply other threads:[~2016-03-09 9:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160309163336.42161c01@x230 \
--to=paul.sokolovsky@linaro.org \
--cc=git@vger.kernel.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).