From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
"Chen, Farrah" <farrah.chen@intel.com>
Subject: Re: [Qemu-devel] [PATCH] build: allow setting a custom GIT binary for transparent proxying
Date: Mon, 23 Oct 2017 09:42:01 +0100 [thread overview]
Message-ID: <20171023084201.GC16472@redhat.com> (raw)
In-Reply-To: <d2200140-bdeb-1746-20a2-15b1fb283c28@redhat.com>
On Fri, Oct 20, 2017 at 03:06:58PM -0500, Eric Blake wrote:
> On 10/20/2017 09:10 AM, Daniel P. Berrange wrote:
> > Some users can't run a bare 'git' command, due to need for a transparent
> > proxying solution such as 'tsocks'. This adds an argument to configure to
> > let users specify such a thing:
> >
> > ./configure --with-git="tsocks git"
> >
> > The submodule script is also updated to give the user a hint about using this
> > flag, if we fail to checkout modules.
>
> Does my hint about using 'git config url.XYZ.insteadof git://...' do the
> trick without needing this patch?
IIUC, that only works if the developer can't access 'git://' URLs but
can access 'https://' URLs. So supporting tunnelling via a tsocks like
program looks like a more generalized solution to me.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-10-23 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 14:10 [Qemu-devel] [PATCH] build: allow setting a custom GIT binary for transparent proxying Daniel P. Berrange
2017-10-20 20:06 ` Eric Blake
2017-10-23 8:42 ` Daniel P. Berrange [this message]
2017-10-20 22:31 ` Philippe Mathieu-Daudé
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=20171023084201.GC16472@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=farrah.chen@intel.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).