qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] WARNING: Savannah back online, do not fetch
Date: Tue, 02 Jun 2009 21:53:45 +0200	[thread overview]
Message-ID: <4A258349.60904@redhat.com> (raw)
In-Reply-To: <4A257D24.3080002@redhat.com>

On 06/02/09 21:27, Avi Kivity wrote:
> As has been noticed, savannah git service is back online with an
> outdated backup.
>
> DO NOT run 'git fetch origin' (or whatever your remote is called). It
> will roll back your local copy to the end of april, and your local copy
> is now an official qemu backup, so don't do anything that can harm it. I
> imagine all the automatic mirrors are now destroyed.

"git pull" didn't rollback, but noticed "your copy is 200+something 
commits ahead".

As far I know it never ever throws away stuff, so the commits will still 
be there.  Remote branches might be f*cked up.  Checking out using local 
branch or by hash should still work fine.

Most recent commits in my local repo:

master: 7696d1ecd0fe4805b630161d276a169c01f80e91
stable: 71c55593c056db5cb80fd40889fa3c5ab9e8ad34

> Hopefully the qemu maintainers will set up an alternative site soon
> where we can happily pull from.

git://git.et.redhat.com/qemu-kraxel.git
branch 'upstream' is savannah/master.

I can push stable if someone needs it.

HTH,
   Gerd

  parent reply	other threads:[~2009-06-02 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 19:27 [Qemu-devel] WARNING: Savannah back online, do not fetch Avi Kivity
2009-06-02 19:47 ` Edgar E. Iglesias
2009-06-02 19:53 ` Gerd Hoffmann [this message]
2009-06-02 21:48 ` All-clear, was " Johannes Schindelin
2009-06-03  4:57   ` Avi Kivity
2009-06-03 10:31     ` Johannes Schindelin
2009-06-03  7:40   ` Anthony Liguori

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=4A258349.60904@redhat.com \
    --to=kraxel@redhat.com \
    --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).