qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
	 Igor Mammedov <imammedo@redhat.com>,
	Ani Sinha <anisinha@redhat.com>,
	 Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	 Eduardo Habkost <eduardo@habkost.net>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	 Peter Hilber <quic_philber@quicinc.com>,
	 "Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>,
	paul <paul@xen.org>
Subject: Re: [PULL 0/1] vmclock queue
Date: Thu, 9 Jan 2025 11:03:13 -0500	[thread overview]
Message-ID: <CAJSP0QWph_F6_4z1bb-gS7maACfHbNDOitmzj54asQkXC=71EA@mail.gmail.com> (raw)
In-Reply-To: <86a600a818cd063397730848957cb2be3be783ae.camel@infradead.org>

On Thu, 9 Jan 2025 at 09:14, David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Thu, 2025-01-09 at 09:01 -0500, Stefan Hajnoczi wrote:
> > On Thu, 9 Jan 2025 at 08:18, David Woodhouse <dwmw2@infradead.org> wrote:
> > >
> > > On Thu, 2025-01-09 at 07:52 -0500, Stefan Hajnoczi wrote:
> > > > On Wed, 8 Jan 2025 at 06:11, David Woodhouse <dwmw2@infradead.org>
> > > > wrote:
> > > >
> > >
> > > > 2. Send pull requests with a GPG-signed tag (git tag --sign) and
> > > > ensure that the repo URL in the email is https:// (the tooling rejects
> > > > unencrypted http:// and git:// repo URLs).
> > >
> > > You mean *or* rather than *and* in that sentence, right? Because if
> > > it's GPG-signed, then I can send it to you over carrier pigeon and you
> > > can validate it; the transport is irrelevant.
> > >
> > > If you really did mean 'and'... is this a new bug in the tooling? Last
> > > time I used Peter's make-pullreq script, it worked fine¹.
> >
> > You're right, both are not required together for security. I still ask
> > for both because we historically had some submaintainers without GPG
> > keys and didn't want them to use unencrypted git:// or http:// URLs.
> > It's easier if everyone does both so I don't have to check whether
> > we've followed the right process depending on their GPG key status. I
> > think QEMU submaintainers have now fully transitioned to GPG keys, so
> > we could probably drop the https:// requirement.
> >
> > If it's not too much trouble to use https:// then that would be easiest.
>
> I tried the 'Advanced Web Server Setup' from
> https://git-scm.com/docs/gitweb  :
>
>   # make the front page an internal rewrite to the gitweb script
>   RewriteRule ^/$  /cgi-bin/gitweb.cgi
>
>   # make access for "dumb clients" work
>   RewriteRule ^/(.*\.git/(?!/?(HEAD|info|objects|refs)).*)?$ \
>                 /cgi-bin/gitweb.cgi%{REQUEST_URI}  [L,PT]
>
> But it seemed to break the gitweb access for URLs of the form
> https://git.infradead.org/users/dwmw2/qemu.git/shortlog/refs/heads/xenfv
> so for the *moment* I have reverted that and filed it in the 'too much
> trouble' bucket. I will take another look at some point though.

That's fine, I'll update my script to accept git://.

Thanks,
Stefan


  reply	other threads:[~2025-01-09 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 11:10 [PULL 0/1] vmclock queue David Woodhouse
2025-01-08 11:10 ` [PULL 1/1] hw/acpi: Add vmclock device David Woodhouse
2025-01-09 12:52 ` [PULL 0/1] vmclock queue Stefan Hajnoczi
2025-01-09 13:18   ` David Woodhouse
2025-01-09 14:01     ` Stefan Hajnoczi
2025-01-09 14:14       ` David Woodhouse
2025-01-09 16:03         ` Stefan Hajnoczi [this message]
2025-01-09 16:10           ` David Woodhouse

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='CAJSP0QWph_F6_4z1bb-gS7maACfHbNDOitmzj54asQkXC=71EA@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=abuehaze@amazon.com \
    --cc=anisinha@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=eduardo@habkost.net \
    --cc=imammedo@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quic_philber@quicinc.com \
    --cc=richard.henderson@linaro.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).