Got there eventually! $ git verify-pack --verbose bar.pack e13e21a1f49704ed35ddc3b15b6111a5f9b34702 commit 220 152 12 03691863451ef9db6c69493da1fa556f9338a01d commit 334 227 164 ... snip ... chain length = 50: 2 objects bar.pack: ok
Now what do I do with it :) On 18 March 2015 at 13:33, Duy Nguyen <pclo...@gmail.com> wrote: > On Wed, Mar 18, 2015 at 8:16 PM, Graham Hay <grahamr...@gmail.com> wrote: >> I created a repo with over 1GB of images, but it works as expected >> (only pushed 3 objects). >> >> Sorry, I must have done something wrong. I put that script in >> ~/Applications, and checked it worked. Then I ran this: >> >> $ GIT_TRACE=2 PATH=~/Applications:$PATH git push --set-upstream origin >> git-wtf > > I think I encountered the same problem. Inserting > --exec-path=$HOME/Applications between "git" and "push" was probably > what made it work for me. Haven't investigated the reason yet. We > really should have an easier way to get this info without jumping > through hoops like this. > -- > Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
