From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: [Qemu-devel] qemu.org vs qemu-project.org
Date: Sun, 19 Nov 2017 20:42:07 -0200 [thread overview]
Message-ID: <20171119224207.GA7484@localhost.localdomain> (raw)
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?
--
Eduardo
next reply other threads:[~2017-11-19 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 22:42 Eduardo Habkost [this message]
2017-11-19 22:46 ` [Qemu-devel] qemu.org vs qemu-project.org Peter Maydell
2017-11-20 10:09 ` Daniel P. Berrange
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=20171119224207.GA7484@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=berrange@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.