Hi Jason,
Today's linux-next fetch of the kgdb tree failed like this:
kgdb: git
fatal: Couldn't find remote ref refs/heads/kgdb-next
fatal: The remote end hung up unexpectedly
So I will use the kgdb tree from yesterday (which actually dates from
May).
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
Stephen Rothwell wrote:
> Hi Jason,
>
> Today's linux-next fetch of the kgdb tree failed like this:
>
> kgdb: git
> fatal: Couldn't find remote ref refs/heads/kgdb-next
> fatal: The remote end hung up unexpectedly
>
> So I will use the kgdb tree from yesterday (which actually dates from
> May).
>
>
In the several years I have been using git, I have never seen it get
corrupted until today.
My local git repository completely bailed, so I am going to reconstruct
the kgdb branches from a new clone. There was no obvious way to recover
my archive.
Here is what it said:
% git push --force
ssh://master.kernel.org/staging/jwessel/linux-2.6-kgdb.git kgdb-next
fatal: bad object 4be3bd7849165e7efa6b0b35a23d6a3598d97465
error: pack-objects died with strange error
error: failed to push some refs to
'ssh://master.kernel.org/staging/jwessel/linux-2.6-kgdb.git'
I'll leave the archive around for a while, as it is nothing more than a
science project as a curiosity of how you recover from such a state.
Jason.
Hi Jason,
On Wed, 22 Jul 2009 22:05:17 -0500 Jason Wessel <[email protected]> wrote:
>
> In the several years I have been using git, I have never seen it get
> corrupted until today.
Ouch!
> My local git repository completely bailed, so I am going to reconstruct
> the kgdb branches from a new clone. There was no obvious way to recover
> my archive.
OK, thanks.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
Stephen Rothwell wrote:
> Hi Jason,
>
>
>> My local git repository completely bailed, so I am going to reconstruct
>> the kgdb branches from a new clone. There was no obvious way to recover
>> my archive.
>>
>
>
As luck would have it, the pull of 2.6.31-rc4 magically fixed the local
archive, so kgdb-next branch is back in sync and updated.
Thanks,
Jason.