From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MBl5i-0006C5-1x for qemu-devel@nongnu.org; Wed, 03 Jun 2009 03:40:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MBl5d-0006Bb-JX for qemu-devel@nongnu.org; Wed, 03 Jun 2009 03:40:53 -0400 Received: from [199.232.76.173] (port=33498 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MBl5d-0006BY-G8 for qemu-devel@nongnu.org; Wed, 03 Jun 2009 03:40:49 -0400 Received: from mx20.gnu.org ([199.232.41.8]:38017) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MBl5d-0001sQ-0C for qemu-devel@nongnu.org; Wed, 03 Jun 2009 03:40:49 -0400 Received: from mail-qy0-f191.google.com ([209.85.221.191]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MBl5b-0007Ri-Ur for qemu-devel@nongnu.org; Wed, 03 Jun 2009 03:40:48 -0400 Received: by qyk29 with SMTP id 29so10402886qyk.4 for ; Wed, 03 Jun 2009 00:40:46 -0700 (PDT) Message-ID: <4A2628FA.9070202@codemonkey.ws> Date: Wed, 03 Jun 2009 02:40:42 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: All-clear, was Re: [Qemu-devel] WARNING: Savannah back online, do not fetch References: <4A257D24.3080002@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Johannes Schindelin Cc: Avi Kivity , "qemu-devel@nongnu.org" 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 > > >