-
Notifications
You must be signed in to change notification settings - Fork 934
NH-3534 #316
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
NH-3534 #316
Conversation
Again leaked commits... But please do not close the pull request. Just do following sequence (assuming that $ git fetch upstream |
C:\nhibernate-core>git reset upstream/master --hard Any thoughts? |
What about this? It will probably be easier for me if I just close this pull request and create a new one. |
What is the output of $ git remote -v ? |
C:\nhibernate-core>git remote -v C:\nhibernate-core>git branch -r |
@rjperes, where is the upstream? Ok, then new actions $ git remote add upstream https://github.com/nhibernate/nhibernate-core.git |
Another attempt, still no luck: C:\nhibernate-core>git remote add upstream https://github.com/nhibernate/nhibernate-core.git C:\nhibernate-core>git fetch --all
C:\nhibernate-core>git checkout NH-3534 C:\nhibernate-core>git reset upstream/master --hard C:\nhibernate-core>git cherry-pick ff8767b |
The replacement for this is #322. |
https://nhibernate.jira.com/browse/NH-3534
Added unit test