Add a --git flag to force git interpretation #215
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Detecting a git hash uses a regular expression to detect a hex
sha or a fixed set of {master, HEAD}. This precludes using tags,
branch names, relative paths (e.g., HEAD~N, etc.). Rather than
trying to make a hash detection scheme that is bullet proof,
this introduces a flag, that the user sets, that forces cloc
to interpret *all* values in a diff as git hashes allowing for
all valid git hash mechanisms.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Detecting a git hash uses a regular expression to detect a hex sha for a fixed set of {master, HEAD}. This precludes using tags, branch names, relative paths (e.g., HEAD~N, etc.). Rather than
trying to make a hash detection scheme that is bullet proof, this introduces a flag, that the user sets, that forces cloc to interpret all values in a diff as git hashes allowing for all valid git hash mechanisms.
There's a distinct possibility that the documentation should be cleaned up. Should it only apply to diff? SHould it apply more broadly?
This change is