qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
	"Alexander Graf" <agraf@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Blue Swirl" <blauwirbel@gmail.com>,
	"Anthony Liguori" <aliguori@amazon.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] openbios.git mirror on git.qemu.org
Date: Tue, 19 May 2015 21:55:12 +0100	[thread overview]
Message-ID: <CAFEAcA_jCmDQ522wsuNj1POFONizBoZHEWTYQTCdL4=WkCAvMA@mail.gmail.com> (raw)
In-Reply-To: <555BA152.5040908@ilande.co.uk>

On 19 May 2015 at 21:47, Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> wrote:
> On 19/05/15 13:55, Andreas Färber wrote:
>
>> Am 19.05.2015 um 12:42 schrieb Stefan Hajnoczi:
>>> Ping.  Should we stick with an old mirror of OpenBIOS for QEMU 2.4 or
>>> switch to the official upstream repo?
>>
>> I don't quite understand the question. OpenBIOS is still using SVN
>> AFAIK. QEMU is using Git, so I thought we always need a Git mirror for
>> submodules? Has the git-svn integration been extended to svn submodules
>> and which versions of git support that?
>
> I'm not sure why submodules make anything different

They mean we can't literally just point our submodule at upstream,
because upstream isn't a git repo and submodules must point
at git repos. (However I think we generally prefer to point at
a git.qemu.org mirror of upstream's repo anyway.)

> , but for an SVN
> repository I can't see why the nightly cron job on git.qemu.org can't
> just run "git svn fetch && git svn rebase" directly against OpenBIOS SVN
> to update its master branch?

Sounds reasonable.

>> Unless I'm missing something, the only question is which mirror do we
>> use, not whether we use a mirror.
>
> The problem at the moment is that the repository on git.qemu.org is
> pointing to a git repository on a plain IP address (with no sensible
> reverse DNS) and so far no-one has admitted ownership. This was a
> problem last week when the repository stopped syncing with OpenBIOS SVN
> trunk and both Stefan and myself had no idea who to contact in order to
> get it fixed.

It's also an obvious problem in terms of tracability and trust
of the code we're shipping to people... We must fix this for 2.4
(or ideally ASAP) I think.

thanks
-- PMM

  reply	other threads:[~2015-05-19 20:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 11:32 [Qemu-devel] openbios.git mirror on git.qemu.org Mark Cave-Ayland
2015-05-19 10:42 ` Stefan Hajnoczi
2015-05-19 12:55   ` Andreas Färber
2015-05-19 20:47     ` Mark Cave-Ayland
2015-05-19 20:55       ` Peter Maydell [this message]
2015-06-09 10:22         ` Stefan Hajnoczi
2015-06-11 22:34           ` Mark Cave-Ayland
2015-06-13  7:53             ` Aurelien Jarno
2015-06-13 15:02               ` Mark Cave-Ayland
2015-06-16 12:55                 ` Stefan Hajnoczi
2015-06-17  8:29                   ` Mark Cave-Ayland

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='CAFEAcA_jCmDQ522wsuNj1POFONizBoZHEWTYQTCdL4=WkCAvMA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aliguori@amazon.com \
    --cc=blauwirbel@gmail.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).