[Qemu-devel] WARNING: Savannah back online, do not fetch

[Qemu-devel] WARNING: Savannah back online, do not fetch

[Avi Kivity]

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.

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

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

Re: [Qemu-devel] WARNING: Savannah back online, do not fetch

[Edgar E. Iglesias]

On Tue, Jun 02, 2009 at 10:27:32PM +0300, 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.
>
> Hopefully the qemu maintainers will set up an alternative site soon where 
> we can happily pull from.

FWIW I've got a tree at git://repo.or.cz/qemu/edde.git with the following
top commits. Only odd thing with that tree is that it also has a microblaze
branch.

master:

commit abc0754527e30acf278765f66d2157b6c75dc549
Author: Edgar E. Iglesias <edgar.iglesias@gmail.com>
Date:   Thu May 28 14:00:49 2009 +0200

    Update maintainer list.
    
    Add myself as maintainer for the microblaze cpu and boards.
    Update list of CRIS machines.
    
    Signed-off-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>


stable-0.10:

commit 71c55593c056db5cb80fd40889fa3c5ab9e8ad34
Author: Chris Lalancette <clalance@redhat.com>
Date:   Mon May 25 16:38:23 2009 +0200

    Allow monitor interaction when using migrate -exec
    
    All,
         I've recently been playing around with migration via exec.  Unfortunately,
    when starting the incoming qemu process with "-incoming exec:cmd", it suffers
    the same problem that -incoming tcp used to suffer; namely, that you can't
    interact with the monitor until after the migration has happened.  This causes
    problems for libvirt usage of -incoming exec, since libvirt expects to be able
    to access the monitor ahead of time.  This fairly simple patch allows you to
    access the monitor both before and after the migration has completed using exec.
    
    (note: developed/tested with qemu-kvm, but applies perfectly fine to qemu)
    
    Signed-off-by: Chris Lalancette <clalance@redhat.com>
    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>

Cheers

Re: [Qemu-devel] WARNING: Savannah back online, do not fetch

[Gerd Hoffmann]

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

All-clear, was Re: [Qemu-devel] WARNING: Savannah back online, do not fetch

[Johannes Schindelin]

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).

Ciao,
Dscho

Re: All-clear, was Re: [Qemu-devel] WARNING: Savannah back online, do not fetch

[Avi Kivity]

Johannes Schindelin wrote:
> It is not as dramatic as you make it sound.
>   

Hey, I'm just spreading some FUD so that we never go back to savannah.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

Re: All-clear, was Re: [Qemu-devel] WARNING: Savannah back online, do not fetch

[Johannes Schindelin]

Hi,

On Wed, 3 Jun 2009, Avi Kivity wrote:

> Johannes Schindelin wrote:
> > It is not as dramatic as you make it sound.
> 
> Hey, I'm just spreading some FUD so that we never go back to savannah.

Oh, I am terribly sorry!

:-)

Ciao,
Dscho

Re: All-clear, was Re: [Qemu-devel] WARNING: Savannah back online, do not fetch

[Anthony Liguori]

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
>
>
>