From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Filesystem corruption at Savannah
Date: Mon, 01 Jun 2009 02:50:02 -0500 [thread overview]
Message-ID: <4A23882A.9050700@codemonkey.ws> (raw)
In-Reply-To: <4A22AA78.1000609@redhat.com>
Avi Kivity wrote:
> Johannes Schindelin wrote:
>
>> So we have a temporary host on repo.or.cz already, and of course, you
>> are free to fork a personal tree.
>>
>
> I'm not sure we can trust the clones since savannah restored from
> backup. Best is to clone a maintainer's personal tree (last one to
> push wins).
A fork of a cloned tree is just a tree setup with a reference to the
cloned tree so you can push whatever you want to it.
I'll push my local tree later today after I talk to the savannah admins.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-06-01 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 7:40 [Qemu-devel] Filesystem corruption at Savannah Stefan Weil
2009-05-29 7:54 ` Anthony Liguori
2009-05-31 14:52 ` Avi Kivity
2009-05-31 15:34 ` Johannes Schindelin
2009-05-31 16:04 ` Avi Kivity
2009-06-01 7:50 ` Anthony Liguori [this message]
2009-06-01 8:02 ` Johannes Schindelin
2009-05-31 19:23 ` Anthony Liguori
2009-05-29 13:25 ` 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=4A23882A.9050700@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).