On Mon, 17 Dec 2007, Mark Fasheh wrote: > Hi, > > Just to "out" myself, I'm the "co-worker" whose name Joel has been > (politely) keeping anonymous. > > On Mon, Dec 17, 2007 at 03:41:24PM -0500, Nicolas Pitre wrote: > > > You may not see a case for actual corruptions, but my coworker > > > updated his tree on a box with 1.5.x, then tried to work on a box with > > > 1.4.x (I think 1.4.2 back then), and ended up with a tree that was > > > unusable. He had to re-clone, and I think he got lucky recovering > > > pending changes (probably using 1.5.x on the branches with the changes, > > > as master was what got broken). > > > > I still claim that there wasn't any corruptions. > > The following description is really vague because this was a while ago: > > Something made my ocfs2.git tree unusable in that I could no longer do > common tasks, such as git-log, etc without getting messages about corrupted > refs. > > I wish I had saved off some of the messages. Sorry. > > I had to re-create my git tree several times before I learned by deduction > that it was the older versions of git on some of the machines that were > writing some sort of incompatible format. Next time please don't hesitate to post your issue on this list. The fix could have been so obvious to many people on the list, saving you time and frustration. In your case I think the "fix" would have consisted of simply running "git repack -a -d" on the machine with the most recent Git version. And if it was a case of real corruption then we certainly would have liked to know about it ASAP. > > Just for fun, just edit some document with Microsoft Office 95, then > > open the same document with Office 2007 and save it with default > > settings. Now try to open it back with Office 95. It won't work. > > Does that mean that the document got corrupted? > > Boy, I hope Microsoft Office isn't our bar for compatiblity here... We can do better of course, like allowing you to still produce the old format with a new version of Git. But sometimes format changes are unavoidable for many good reasons. Nicolas - 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
