Dear diary, on Fri, Oct 27, 2006 at 04:27:05PM CEST, I got a letter where Nicolas Pitre <nico@xxxxxxx> said that... > On Thu, 26 Oct 2006, Shawn Pearce wrote: > > OK so the repository won't get corrupted but the repack would be > > forced to abort. > > Maybe this is the best way out? Abort git-repack with "a fetch is in > progress -- retry later". No one will really suffer if the repack has > to wait for the next scheduled cron job, especially if the fetch doesn't > explode packs into loose objects anymore. I don't really like this that much. Big projects can have 10 commits per hour on average, and they also take potentially long time to repack, so you might get to never really repack them. -- 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