[RFC] Improve speed of git effort #392
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
|
Thank you. |
hemanth
added a commit
that referenced
this pull request
Jul 10, 2015
[RFC] Improve speed of git effort
Collaborator
Author
|
Please don't merge in my WIP-branch from my RFC pull request next time without letting me know first. |
Collaborator
Reverting will result in merge conflict, can you please do a new PR, sorry for the inconvenience. |
Collaborator
Author
|
It is working as it is now, but I will open a new PR with some small touch ups. I guess it was a little late when I wrote that comment, didn't mean to sound harsh. |
Collaborator
|
👍 |
Closed
tardypad
pushed a commit
to tardypad/git-extras
that referenced
this pull request
Jul 13, 2016
[RFC] Improve speed of git effort
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.
Speedup is gained by two main edits
This PR will conflict with #390 and/or #391, so I will do a rebase if those are merged.
I have tested this with the Hugo blog engine, with 24 seconds on git effort vs. 7 seconds with this patch. (Those numbers are obviously to be taken with a grain of salt) This was on my computer with two physical cores.