Hi, On Tue, 13 Feb 2007, Theodore Tso wrote: > On Tue, Feb 13, 2007 at 01:27:03AM -0800, Junio C Hamano wrote: > > I noticed while scanning #git log that it appears that pack-refs > > was run in your public repo and some people cannot clone over > > dumb protocols with older git. > > > > commit 2986c02217f98809d8990e7679edf0f5d99f904d > > Author: Junio C Hamano <junkio@xxxxxxx> > > Date: Wed Nov 22 22:24:09 2006 -0800 > > > > git-fetch: fix dumb protocol transport to fetch from pack-pruned ref > > > > was the first revision that aligned dumb protocol clients with > > pack-ref; unfortunately anything older will not find the ref > > that was packed. > > Stupid question. Suppose someone has run git pack-refs on a > repository. What is the recommended way to reverse the process. Is > the answer is to clone the repository and then throw away the original > one? Is there another way to do it? The easiest way I found here was to do git-for-each-ref | while read sha1 tag name; do git update-ref -m "undo pack-ref" $name $sha1 done Beware: this is tested once, and copied from memory. Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html