[英]When I write out a repository state with `--fossilize` in reposurgeon, does 'read' restore those markers?
When converting a repository using reposurgeon
and I write a state into the git-fast-export
by doing: 当使用reposurgeon
转换存储库时,我通过执行以下操作将状态写入git-fast-export
:
prefer git
write --fossilize >nameofdump.fi
will a subsequent: 将随后:
read <nameofdump.fi
restore the additional markers that get dumped using the --fossilize
option, or do I have to use a separate "fossils file" via: 恢复使用--fossilize
选项转储的其他标记,或者我必须通过以下方式使用单独的“化石文件”:
fossils write >nameofdump.fo
and: 和:
fossils read <nameofdump.fo
respectively? 分别?
The point is that since I am converting from SVN I need to make use of the fossil IDs as the documentation calls them, which correspond to the respective global revision ID in SVN. 关键是,由于我是从SVN转换的,因此我需要使用化石ID,因为文档称为它们,它们对应于SVN中的各个全局修订版ID。
更加了解( reposurgeon
3.10的)代码之后,我可以得出结论, 没有 write --fossilize
没有相应的read
操作,而普通read
并不关心# Fossil-ID: ...
git-fast-import
注释write --fossilize
产生的git-fast-import
流。
Author of reposurgeon here. 这里是reposurgeon的作者。
The support for Fossil was written from specifications; 对Fossil的支持来自规范。 I have never really tested it. 我从来没有真正测试过。
If the above is still a live issue, please file a bug repiort againat reposurgeon abd I'll fix it. 如果上述问题仍然存在,请在reposurgeon再次提交bug repiort,我将予以修复。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.