From: Peter Maydell <peter.maydell@linaro.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Brad Hards <bradh@frogmouth.net>, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] stale savannah git repo (was: Re: KVM call agenda for April 05)
Date: Thu, 22 Sep 2011 15:37:05 +0100 [thread overview]
Message-ID: <CAFEAcA9hJ0JCq0TQOzN3dA9-icxJYzCg267X5-XS1oPe7_P+sg@mail.gmail.com> (raw)
In-Reply-To: <4E7B4770.4030401@codemonkey.ws>
On 22 September 2011 15:34, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 09/22/2011 09:20 AM, Peter Maydell wrote:
>> Hup! Somebody here was confused by the now-ancient-but-not-deleted
>> savannah git repo again today. Do we have a timescale for getting
>> rid of it, reinstating the qemu.org web interface to git, etc ?
>
> OSUOSL had a security breach as part of the kernel.org intrusion so all
> plans to move are on hold until that whole mess gets straightened out.
Ah :-(
> The reason I don't have an auto mirror set up with Savannah is that I don't
> want to publish my private key on a remote server (and the kernel.org break
> in is a good example of why no one should :-)).
If we're not going to have an updated mirror I think we should just
delete the savannah repo -- an apparently authoritative but actually
stale repo is worse than useless.
-- PMM
next prev parent reply other threads:[~2011-09-22 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 10:14 [Qemu-devel] stale savannah git repo (was: Re: KVM call agenda for April 05) Peter Maydell
2011-06-14 13:24 ` Anthony Liguori
2011-09-22 14:20 ` Peter Maydell
2011-09-22 14:34 ` Anthony Liguori
2011-09-22 14:37 ` Peter Maydell [this message]
2011-09-22 14:55 ` Jan Kiszka
2011-09-22 15:04 ` Anthony Liguori
2011-09-22 18:27 ` [Qemu-devel] stale savannah git repo Stefan Weil
2011-09-23 11:53 ` Andreas Schwab
2011-09-23 16:09 ` Stefan Weil
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=CAFEAcA9hJ0JCq0TQOzN3dA9-icxJYzCg267X5-XS1oPe7_P+sg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=bradh@frogmouth.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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.