David Mansfield <david@xxxxxxxxxx> writes: > Also, how does the git packaging (non-rpm version) specify and/or > guarantee dependencies are at a certain version anyway? We cannot really do much with the old cvsimport out in the field, but I was wondering more about automatic detection in new cvsimport. The way I read 02-cvsps-implement-branch-point-detection.patch, you have three cases: - "Ancestor branch:" is not followed by "Branches:" before "Log:" (old cvsps); - "Ancestor branch:" is followed by "Branches:" before "Log:" (new); - "Branches:" without "Ancestor branch:" (new); So perhaps your 04-cvsimport-redo-branch-creation-process.patch, instead of ignoring what "Ancestor branch:" said, can remember it has seen what "ancestor" (which may be a bit off) information it was given, and when you see "Log:" (by that time, you either have seen "Branches:" from new cvsps, or you didn't see it from old cvsps) you can decide which vintage of cvsps it is reading from. Or something like that. -- 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
