Fix some fatal for git-line-summary #368
Merged
Conversation
This file contains hidden or 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
Collaborator
|
@zix Thanks! Could you please squash the commits? |
1. Fix print format with special characters 2. Fix Fatal when exist special characters in git blame output 3. Fix raise error when exist not committed new files
zlx
force-pushed
the
feature/strong_line_summary
branch
from
e33a1f3 to
72f08b1
Compare
Contributor
Author
|
@hemanth of cause! |
Collaborator
|
👍 |
hemanth
added a commit
that referenced
this pull request
May 9, 2015
Fix some fatal for git-line-summary
Contributor
Author
|
Nice. Thank you |
Closed
tardypad
pushed a commit
to tardypad/git-extras
that referenced
this pull request
Jul 13, 2016
Fix some fatal for git-line-summary
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fatal: no such path 'newfilename' in HEAD