From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] qemu.org vs qemu-project.org
Date: Mon, 20 Nov 2017 10:09:43 +0000 [thread overview]
Message-ID: <20171120100943.GC31943@redhat.com> (raw)
In-Reply-To: <CAFEAcA-C3nwLrOcgFgN6t_UpzVr8xLJw0VE2Afe8abt2_U5k2Q@mail.gmail.com>
On Sun, Nov 19, 2017 at 10:46:20PM +0000, Peter Maydell wrote:
> On 19 November 2017 at 22:42, Eduardo Habkost <ehabkost@redhat.com> wrote:
> > Hi,
> >
> > I've noticed that README, MAINTAINERS .gitmodules, and other
> > files in qemu.git are pointing to qemu-project.org, while the
> > QEMU web site and other files in qemu.git are pointing to
> > qemu.org.
> >
> > I assume that the situation mentioned in commit
> > 8593898109 ("Use qemu-project.org domain name") has improved.
> > Should we update the existing files to point to qemu.org, now?
>
> Yeah, we decided that we should go with qemu.org as the
> main name (so qemu-project.org urls redirect to it).
> We should probably generally move to qemu.org in our
> documentation, at least. I'm not sure if there are
> any unfortunate side-effects to changing a .gitmodules
> URL ?
Quite possibly - we would have todo some testing to see what, if
any, fallout there is.
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 :|
prev parent reply other threads:[~2017-11-20 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 22:42 [Qemu-devel] qemu.org vs qemu-project.org Eduardo Habkost
2017-11-19 22:46 ` Peter Maydell
2017-11-20 10:09 ` Daniel P. Berrange [this message]
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=20171120100943.GC31943@redhat.com \
--to=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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 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.