On Tue, Mar 6, 2012 at 21:49, Neal Kreitzinger <nkreitzinger@xxxxxxxxx> wrote: > On 3/6/2012 10:09 AM, Barry Roberts wrote: > Be aware that you are rewriting history. I assume this is published > history that you are going to run filter-branch on. That means everyone who > cloned from the old history (pre-filter-branch), not to mention those who > also have WIP based on the old history, will need to somehow adjust to the > new history. Does something other than git-fsck actually check whether the collection of blobs you're getting from the remote when you clone have sensible sha1's? What'll happen if he replaces that 550MB blob with a 0 byte blob but hacks the object store so that it pretends to have the same sha1? Of course the real solution to this issue is to either rewrite history, or to change Git to support partially fetching the old blobs in your project. -- 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