qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Moving seabios-hppa git submodule to use a qemu.org mirror
Date: Mon, 19 Mar 2018 15:15:34 -0400	[thread overview]
Message-ID: <20180319191534.GM12302@localhost.localdomain> (raw)
In-Reply-To: <alpine.BSF.2.21.1803191426370.9395@zero.eik.bme.hu>

On Mon, Mar 19, 2018 at 02:32:22PM +0100, BALATON Zoltan wrote:
> On Mon, 19 Mar 2018, Peter Maydell wrote:
> >On 21 February 2018 at 05:27, Jeff Cody <jcody@redhat.com> wrote:
> >>On Tue, Feb 20, 2018 at 06:43:22PM +0000, Peter Maydell wrote:
> >>>I just noticed that we seem to have acquired another git
> >>>submodule that isn't pointing to a qemu.org git url:
> >>>
> >>>[submodule "roms/seabios-hppa"]
> >>>        path = roms/seabios-hppa
> >>>        url = git://github.com/hdeller/seabios-hppa.git
> >>>
> >>>Jeff, could we set up so we can mirror this repo on qemu.org?
> >>>Then we can send a patch to update the .gitmodules to point to it.
> >>>
> >>
> >>Yes, of course... Although Paolo has suggested making it a branch of the
> >>existing SeaBIOS repo instead.  But I can go ahead and get the clone setup,
> >>in case we go that route.
> >
> >Hi; can we get the mirror set up for seabios-hppa, and also for
> >the other new repo:
> >git://github.com/zbalaton/u-boot-sam460ex
> 
> I'd suggest to move the u-boot-sam460ex repo to qemu repo completely instead
> of mirrorring it. I don't intend to change it in the future (apart from
> maybe occasional bugfixes if needed which chould be submitted as patches) so
> no need to keep an external repo and mirror it when it could be held in qemu
> as primary.
> 
> Please let me know how you decide, I can then remove the the above repo and
> refer to the qemu one in the future if you move it there or keep the current
> one up if you choose to mirror it.
> 

I went ahead and created it as a mirror.  If there is consensus on moving it
to qemu.org as a primary host, I can convert it (and I'll need to set you up
an account on qemu.org as well at that point, for those occasional
bugfixes).

For now, keep your repo up as a primary source until we know if we are
moving it to qemu.org rather than just mirroring it.

-Jeff

  reply	other threads:[~2018-03-19 19:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 18:43 [Qemu-devel] Moving seabios-hppa git submodule to use a qemu.org mirror Peter Maydell
2018-02-20 21:41 ` BALATON Zoltan
2018-02-20 21:55   ` Paolo Bonzini
2018-02-20 22:12     ` BALATON Zoltan
2018-02-20 22:01 ` Paolo Bonzini
2018-02-21  5:27 ` Jeff Cody
2018-03-19 13:19   ` Peter Maydell
2018-03-19 13:32     ` BALATON Zoltan
2018-03-19 19:15       ` Jeff Cody [this message]
2018-03-19 21:36         ` BALATON Zoltan
2018-03-19 19:06     ` Jeff Cody
2018-03-20 17:54       ` Paolo Bonzini
2018-03-21 15:09         ` Jeff Cody
2018-03-21 15:21           ` Paolo Bonzini
2018-03-21 15:34             ` Jeff Cody

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=20180319191534.GM12302@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=balaton@eik.bme.hu \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).