On Wed, 22 Mar 2006, Jan-Benedict Glaw wrote: > > I'm currently working a lot with Binutils and GCC and wanted to import > those two projects into GIT trees, but both of them failed. If anybody > wants to have access to the half-finished GIT trees, please let me > know: Well, I can re-create your error.. > Switching from origin to gdb-4_18-branch > usage: git-read-tree (<sha> | -m [--aggressive] [-u | -i] <sha1> [<sha2> [<sha3>]]) > read-tree failed: 33024 That's a horrible error message, and the reason for it is that no "gdb-4_18-branch" exists. There's a _tag_ called "gdb-4_18", and there's a branch called "GDB_4_18", and they actually point to two _different_ commits (both "Initial creation of sourceware repository"). The commits actually have identical trees, but they're different, because they have different times - by 50 seconds. Gaah. Looking at cvsps output (from cvsps --norc -u -A -v -d --cvsdirect --root :pserver:anoncvs@xxxxxxxxxxxxxx:/cvs/src src > cvsps.out 2> cvsps.err it's "PatchSet 104" (well, for me it is, I have a hacked cvsps, so it might not be that for you), which creates the "gdb-4_18-branch", but it appears that cvsps hasn't actually figured out any "Ancestor branch" for that commit. What a crock. Anyway, it's clearly a cvsps bug (mentioning a new branch without the _source_ of that branch). Equally clearly, "git cvsimport" is being an ass about then failing so totally on it. I'll try to take a look at why cvsps does that. Linus - : 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