> - your "git pull" failed, because it was fetching objects that were > corrupt in your local database - and the rule is that local objects > ALWAYS override remote objects. That's an important security thing (a > "pull" is _never_ allowed to overwrite something you already have, and > it doesn't matter if it's corrupt or not, you're not ever going to have > a "git pull" overwriting old data) ... > That's true robustness. > > Linus OK, now that I know what happened, this makes sense to me. But I'd like to understand whether what created this in the first place: > > - you had gotten some corrupt objects due to the disk filling up > (probably during the pull that thus populated the object database with > partially written objects) > > In particular, the 4d4d30be967d3284cbf59afd4fba6ab536e295f5 object was > corrupt. fsck gave a confusing error message: > > error: 4d4d30be967d3284cbf59afd4fba6ab536e295f5: object not found > error: c03590b581d51d5fa43adbef9415e935d0229412: object not found > > which is really because the _file_ for that object does exist, but the > file doesn't actually contain the object it expects (due to > corruption), so the object wasn't "found". is something expected? -- MST - 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