Michael Haggerty <mhag...@alum.mit.edu> writes: > Yes, it can be handy to start loading the first "blobfile" in parallel > with the later stages of the conversion, before the second "dumpfile" is > ready. In that case the user needs to pass --export-marks to the first > fast-import process to export marks on blobs so that the marks can be > passed to the second fast-import via --import-marks. > > So the proposed change would break a documented use of cvs2git. > > Making the export of blob marks optional would of course be OK, as long > as the default is to export them.
Thanks for a concise summary. Your use case fits exactly what Felipe conjectured as the nonexistent minority. An option that lets the caller say "I only care about marks on these types of objects to be written to (and read from) the exported marks file" would help Felipe's use case without harming your use case, and would be a sane and safe way to go. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html