Thanks to visit codestin.com
Credit goes to github.com

Skip to content

rebase: additional setup tests of exotic behavior #3623

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 9, 2016

Conversation

ethomson
Copy link
Member

Test some additional exotic rebase setup behavior: that we are
able to set up properly when already in a detached HEAD state,
that the caller specifies all of branch, upstream and onto,
and that the caller specifies branch, upstream and onto by ID.

Test some additional exotic rebase setup behavior:  that we are
able to set up properly when already in a detached HEAD state,
that the caller specifies all of branch, upstream and onto,
and that the caller specifies branch, upstream and onto by ID.
@ethomson
Copy link
Member Author

@carlosmn I was trying to get a repro case for the issue you mentioned to me in chat, where you got into a strange situation using libgit2's rebase. Unfortunately, I do not remember the details, so I banged out a couple of unit tests around what I thought you had said. These all match up with git's behavior, though.

Could you remind me what you did that was odd?

@carlosmn
Copy link
Member

The problem shows up when using git_annotated_commit_lookup() and then calling git_rebase_commit() or git_rebase_abort(), which I don't see here.

carlosmn added a commit that referenced this pull request Mar 9, 2016
rebase: additional setup tests of exotic behavior
@carlosmn carlosmn merged commit 2ba9a0d into libgit2:master Mar 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants