Hi, I've been using a daily cron job running parsecvs to convert an uber CVS tree into git. It works quite well and is substantially faster than all the other methods I have tried. It also re-creates the same history every time which is something I haven't managed to do with the other tools. Anyway today I noticed it had failed to import a sub-directory of the project (not a bit I usually build). However looking at the import log from parsecvs I see that the file was read by parsecvs. It looks as though it should have made it into the git repo. The only thing that seems different from the other modules is that the files where imported once and don't seem to have been touched since. This may of caused parsecvs to get confused? Questions: 1. Has anyone seen this behaviour with parsecvs? 2. Is there any way to list all the tree objects in a repo so I can search to see if the files exist in a tree but just not this branch? -- Alex, homepage: http://www.bennee.com/~alex/ -- 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
