From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
"Alexander Graf" <agraf@suse.de>,
"Andreas Färber" <afaerber@suse.de>,
"Anthony Liguori" <aliguori@amazon.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] openbios.git mirror on git.qemu.org
Date: Thu, 11 Jun 2015 23:34:39 +0100 [thread overview]
Message-ID: <557A0CFF.8080601@ilande.co.uk> (raw)
In-Reply-To: <20150609102221.GB27900@stefanha-thinkpad.redhat.com>
On 09/06/15 11:22, Stefan Hajnoczi wrote:
> On Tue, May 19, 2015 at 09:55:12PM +0100, Peter Maydell wrote:
>> 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.
>
> Okay. I will set up a cronjob to use git-svn to grab the latest
> OpenBIOS from upstream soon.
Hi Stefan,
As it's freeze coming up, I need to send an OpenBIOS pull request fairly
soon. Do you need anything from me to get this done beforehand?
ATB,
Mark.
next prev parent reply other threads:[~2015-06-11 22:35 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
2015-06-09 10:22 ` Stefan Hajnoczi
2015-06-11 22:34 ` Mark Cave-Ayland [this message]
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=557A0CFF.8080601@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=blauwirbel@gmail.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.