Dear diary, on Thu, Apr 21, 2005 at 01:06:09AM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... > After getting the latest tarball, and make, make install: > > Tree change: > 55f9d5042603fff4ddfaf4e5f004d2995286d6d3:a46844fcb6afef1f7a2d93f391c82f08ea322221 > *100755->100755 blob > a78cf8ccab98861ef7aecb4cb5a79e47d3a84b67->74b4083d67eda87d88a6f92c6c66877bba8bda8a > gitcancel.sh > Tracked branch, applying changes... > Fast-forwarding 55f9d5042603fff4ddfaf4e5f004d2995286d6d3 -> > a46844fcb6afef1f7a2d93f391c82f08ea322221 > on top of 55f9d5042603fff4ddfaf4e5f004d2995286d6d3... > patch: **** Only garbage was found in the patch input. > > This may be a harmless message, but I thought I'd bring it to your attention.
This _is_ weird. What does $ git diff -r 55f9d5042603fff4ddfaf4e5f004d2995286d6d3:a46844fcb6afef1f7a2d93f391c82f08ea32222 tell you? What if you feed it to patch -p1? What if you feed it to git apply? Thanks, -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html