-
I can get the required information using the git wrapper:
However this is too slow when run on in a loop over every file in a set of refs due to process execution overhead. |
BetaWas this translation helpful?Give feedback.
Answered by Byron Aug 7, 2024
Replies: 1 comment
-
The algorithm can't be used - instead one should traverse each commit, see which files were changed, and remove those from the set of all currently tracked files while associating the hash of the commit. Repeat until the set of tracked files is empty. This will traverse the commit-graph once, in the worst case, and diff the trees of each commit. But there isn't really any other way. |
BetaWas this translation helpful?Give feedback.
0 replies
Answer selected byali1234
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
The algorithm can't be used - instead one should traverse each commit, see which files were changed, and remove those from the set of all currently tracked files while associating the hash of the commit. Repeat until the set of tracked files is empty.
This will traverse the commit-graph once, in the worst case, and diff the trees of each commit. But there isn't really any other way.