From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] Use qemu.org domain name
Date: Mon, 20 Nov 2017 14:29:36 +0000 [thread overview]
Message-ID: <20171120142936.GM31943@redhat.com> (raw)
In-Reply-To: <CAFEAcA-A4T_q5+AMuAmEAGCHA+BXaXXUqLiu2tvK6MOCiniZBQ@mail.gmail.com>
On Mon, Nov 20, 2017 at 02:26:15PM +0000, Peter Maydell wrote:
> On 20 November 2017 at 14:22, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > The owner of qemu.org has delegated authority to modify DNS records to
> > the QEMU Project. This has allowed us to use the domain name without
> > worries about IP address changes or technical issues disrupting service.
> > The issues described in commit 859389810910f232188675d2f10b15f1aad77660
> > ("Use qemu-project.org domain name") have therefore been mitigated.
> >
> > This patch switches back to consistently using qemu.org instead of
> > qemu-project.org.
> >
> > Note that git-submodule(1) does not detect URL changes. The following
> > commands clean up all submodules to ensure you will use the latest URLs:
> >
> > $ git submodule deinit . # you'll be warned if you have local changes
> > $ rm -rf .git/modules # also clear cached .git/ directories
>
> Are we really sure we want to do this in the middle of
> a release? I'd be rather happier if we fixed the documentation
> now and saved messing around with .gitmodules until afterwards...
We can probably also put a workaround in scripts/git-submodules.sh to
automatically change the git origin of all currently checked out
submodules, so that the change doesn't affect devs at all.
IOW, I'd suggest respinning this series without the submodule
changes, as that's a functional change, and the rest of this
is all non-functional changes.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-11-20 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 14:22 [Qemu-devel] [PATCH 0/2] Update qemu.org domains Stefan Hajnoczi
2017-11-20 14:22 ` [Qemu-devel] [PATCH 1/2] Use qemu.org domain name Stefan Hajnoczi
2017-11-20 14:26 ` Peter Maydell
2017-11-20 14:29 ` Daniel P. Berrange [this message]
2017-11-21 10:16 ` Stefan Hajnoczi
2017-11-20 14:54 ` Eduardo Habkost
2017-11-20 14:22 ` [Qemu-devel] [PATCH 2/2] Use HTTPS for qemu.org and other domains Stefan Hajnoczi
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=20171120142936.GM31943@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--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).