我正在阅读 the docs .在关于 Mercurial 的书签系统的部分，我读到:
Bookmarks can be used as an alternative to NamedBranches for tracking multiple lines of development. Systems like Mercurial, CVS, and Subversion store their branch information as a permanent part of each commit. This is useful for future auditing of long-lived branches, as it’s always possible to identify which branch a commit was introduced on. Git, by contrast, has “branches” that are not stored in history, which is useful for working with numerous short-lived feature branches, but makes future auditing impossible.
我尝试在网上搜索与 Mercurial 相关的“ future 审计”，但几乎每篇文章都有与上面引用的完全相同的文本，就好像他们都从同一个地方偷走了这个文档。
这个在 git 中被认为是不可能的神秘的“ future 审计”是什么？
谢谢。
最佳答案
这与“Deleting git branch looses audit”中提到的审计相同:
git 中的分支可以随时删除或重命名。
if the merge was not a fast-forward you will see that the commits were made to a branch that was later merged, but you won't know what the branch was originally called.
您可以在 More On Mercurial vs. Git (with Graphs!) 中看到它的插图(2011)
关于git - Mercurial - "future auditing"是什么？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/32492973/