Re: [Qemu-devel] openbios.git mirror on git.qemu.org

[Stefan Hajnoczi]

On Tue, May 19, 2015 at 09:55:12PM +0100, Peter Maydell wrote:
> On 19 May 2015 at 21:47, Mark Cave-Ayland <address@hidden> 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.

Stefan

pgpIjExf3TwXE.pgp
Description: PGP signature