Let's target infrastructure / plumbing for now. First up: RevWalk. #155
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
scouten
added a commit
that referenced
this pull request
Jun 6, 2019
* master: Let's target infrastructure / plumbing for now. First up: RevWalk. (#155) # Conflicts: # notes/porting_roadmap.txt
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.
Changes in This Pull Request
Based on some feedback from initial reviewers, I'm shifting focus from porting entire jgit command APIs to working on core infrastructure.
RevWalkis heavily used by other portions of jgit, so that seems like a good initial focus.Checklist
All applicable changes have been documented.n/aThere is test coverage for all changes.n/aAny code ported from jgit maintains all existing copyright notices.n/aThe Eclipse Distribution License header text is included in all new source files.n/aIf new files are ported from jgit, the path to the corresponding file(s) is included in the header comment.n/aAnyn/aTO DOitems (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.