| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4A67D36D.8070209@windriver.com> Date: Wed, 22 Jul 2009 22:05:17 -0500 From: Jason Wessel <jason.wessel@...driver.com> To: Stephen Rothwell <sfr@...b.auug.org.au> CC: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: linux-next: kgdb tree fetch failure 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists