qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, peter.maydell@linaro.org
Subject: Re: [PATCH 1/5] configure: remove --with-git= option
Date: Tue, 30 May 2023 13:17:03 +0100	[thread overview]
Message-ID: <ZHXpP29aPqSit6re@redhat.com> (raw)
In-Reply-To: <CABgObfaT_vOxPaF_GXzGyDD5fNoKZDJU1FEb4_B70C1ddDxPjQ@mail.gmail.com>

On Tue, May 30, 2023 at 02:03:11PM +0200, Paolo Bonzini wrote:
> On Tue, May 30, 2023 at 1:58 PM Thomas Huth <thuth@redhat.com> wrote:
> > The commit cc84d63a42e31c2a that introduce this switch gave a
> > rationale:
> >
> >      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"
> 
> I see, thanks for the additional information--it makes sense to
> include it in the commit message.
> 
> My impression is that the "smart HTTP" protocol has made this concern
> less important. Smart HTTP was introduced in 2009, but back in 2017
> the git protocol running on port 9418 was still quite common. QEMU
> itself switched from git to https in 2018 with commit a897f22b596b62,
> about a year after --with-git was introduced.

Here is the original thread:

  https://lists.nongnu.org/archive/html/qemu-devel/2017-10/msg05005.html

yes it was about 'git://' protocol, and yes, creating a wrapper
script call 'git' was a viable option too.  I just added --with-git
as a convenience.

> > But if the plain "git" command is unusable on their system,
> > they should likely introduce a proper wrapper on their end
> > for this command anyway, so IMHO it's ok if we remove this
> > again. Daniel, what do you think?
> 

With 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 :|



  reply	other threads:[~2023-05-30 12:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27  9:28 [PATCH 0/5] meson: replace submodules with wrap files Paolo Bonzini
2023-05-27  9:28 ` [PATCH 1/5] configure: remove --with-git= option Paolo Bonzini
2023-05-30 11:58   ` Thomas Huth
2023-05-30 12:03     ` Paolo Bonzini
2023-05-30 12:17       ` Daniel P. Berrangé [this message]
2023-05-30 12:18   ` Daniel P. Berrangé
2023-05-27  9:28 ` [PATCH 2/5] configure: rename --enable-pypi to --enable-download, control subprojects too Paolo Bonzini
2023-05-27 16:49   ` BALATON Zoltan
2023-05-27 19:18     ` Paolo Bonzini
2023-05-30 12:00   ` Thomas Huth
2023-05-27  9:28 ` [PATCH 3/5] meson: subprojects: replace submodules with wrap files Paolo Bonzini
2023-05-30 12:23   ` Daniel P. Berrangé
2023-05-30 12:51     ` Paolo Bonzini
2023-05-30 12:54       ` Daniel P. Berrangé
2023-05-27  9:28 ` [PATCH 4/5] configure: check for SLOF submodule before building pc-bios/s390-ccw Paolo Bonzini
2023-05-30 12:04   ` Thomas Huth
2023-05-30 12:53     ` Paolo Bonzini
2023-05-30 13:00       ` Thomas Huth
2023-05-27  9:28 ` [PATCH 5/5] meson: subprojects: replace berkeley-{soft, test}float-3 with wraps Paolo Bonzini
2023-05-30 12:18 ` [PATCH 0/5] meson: replace submodules with wrap files Thomas Huth
2023-05-30 12:57   ` Daniel P. Berrangé
2023-05-30 13:22     ` Paolo Bonzini
2023-05-30 12:30 ` Daniel P. Berrangé
2023-05-30 12:47   ` Paolo Bonzini

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=ZHXpP29aPqSit6re@redhat.com \
    --to=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).