From: Anthony Liguori <anthony@codemonkey.ws>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Avi Kivity <avi@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: All-clear, was Re: [Qemu-devel] WARNING: Savannah back online, do not fetch
Date: Wed, 03 Jun 2009 02:40:42 -0500 [thread overview]
Message-ID: <4A2628FA.9070202@codemonkey.ws> (raw)
In-Reply-To: <alpine.DEB.1.00.0906022343340.26154@pacific.mpi-cbg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Tue, 2 Jun 2009, 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.
>>
>
> It is not as dramatic as you make it sound.
>
> In the most usual setup, the Git clones will _all_ have reflogs set up.
> So if you call
>
> $ git log -g origin/master
>
> it will show the history of _this clone's_ origin/master. IOW you will
> see exactly where a "forced update" reset your locally cached
> origin/master, and you will still have the formerly valid revision.
>
> So no, there is no real harm done if you happened to "git fetch", even if
> nobody pushed the up-to-date versions again.
>
> Oh, BTW, congratulations to switching away from Subversion just in time;
> it is much easier to recover with Git: just push a newer revision (and
> even if you should forget a revision, if somebody merges the former HEAD
> and pushes, all is well in Git land).
>
The tree on Savannah has been restored to right before the outage. All
the mirrors should now be okay too.
Regards,
Anthony Liguori
> Ciao,
> Dscho
>
>
>
prev parent reply other threads:[~2009-06-03 7:40 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
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 [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=4A2628FA.9070202@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Johannes.Schindelin@gmx.de \
--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 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.