On Mon, Nov 13, 2006 at 08:54:14PM CET, Shawn Pearce wrote: > Alex Riesen <fork0@xxxxxxxxxxx> wrote: > > Junio C Hamano, Sun, Nov 12, 2006 20:41:23 +0100: > > > Since this is not everyday anyway, a far easier way would be to > > > clone-pack from the upstream into a new repository, take the > > > pack you downloaded from that new repository and mv it into your > > > corrupt repository. You can run fsck-objects to see if you got > > > back everything you lost earlier. > > > > I get into such a situation annoyingly often, by using > > "git clone -l -s from to" and doing some "cleanup" in the > > origin repository. For example, it happens that I remove a tag, > > or a branch, and do a repack or prune afterwards. The related > > repositories, which had "accidentally" referenced the pruned > > objects become "corrupt", as you put it. > > > > At the moment, if I run into the situation, I copy packs/objects from > > all repos I have (objects/info/alternates are useful here too), run a > > fsck-objects/repack and hope nothing is lost. It works, as I almost > > always have "accidental" backups somewhere, but is kind of annoying to > > setup. A tool to do this job more effectively will be very handy (at > > least, it wont have to copy gigabytes of data over switched windows > > network. Not often, I hope. Not _so_ many gigabytes, possibly). cg-fetch -f locally or over HTTP should be able to fix that up, if used cleverly. > One of my coworkers recently lost a single loose tree object. > We suspect his Windows virus scanner deleted the file. :-( > > Copying the one bad object from another repository immediately fixed > the breakage caused, but it was very annoying to not be able to run a > "git fetch --missing-objects" or some such. Fortunately it was just > the one object and it was also still loose in another repository. > scp was handy. :-) If it's over ssh, this is still where the heavily dusty (and heavily "plumby") git-ssh-fetch command is useful, since it can get passed an undocumented --recover argument and then it will fetch _all_ the objects you are missing, not assuming anything. Perhaps I should reintroduce support for git-ssh-fetch to cg-fetch to be used in case of -f over SSH. But it would be silly if I did that and next Git would remove the command from its suite. Junio, what's its life expectancy? I guess this usage scenario is something to take into account when thinking about removing it, I know that I wanted to get rid of it in the past but now my opinion is changing. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) - 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