What is a “future audit”?

Question

I read the docs . In the Mercurial bookmarking section, I read the following:

Bookmarks can be used as an alternative to NamedBranches to track multiple development lines. Systems such as Mercurial, CVS, and Subversion retain their branch information as a permanent part of each commit. This is useful for future audits of long-lived branches, since you can always determine which branch a commit to was entered on. Git, on the contrary, has branches that are not stored in the history, which is useful for working with numerous short-lived branch functions, but makes future audits impossible.

I tried to find a “future audit” related to mercurial on the Internet, but almost every article has the same text as above, as if they all stored this documentation from the same place.

What is this mysterious “future audit” that is supposedly impossible in git?

Thanks.

Answer 1

“Future audit” is not a technical term; it is just another way to say “for future use”, “for future analysis”. This is why googling for mercurial future auditingwill not give you many useful results.

, Git , --no-ff git merge, . , , , . , Git Flow --no-ff .

Git - Flow. --no-ff , , .

Answer 2

, , git :

git .

, , , , , .

Mercurial vs. git ( !) (2011)

Answer 3

- , , , , . commit-msg, :

    sed -si "/^###audit identifer:.*###/d
         \$ s/.*\$/&\\n###audit identifier: $(printf %s `git config x-workdata.bugid`)###" "$1"

commit-msg ( ), x-workdata.bugid.

, (a) , , () , id , . , , , , - , ? .