Skip to content
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

Kmcuda for windows bugfixes #62

Open
wants to merge 24 commits into
base: master
Choose a base branch
from

Conversation

pavlexander
Copy link

The changes that were suggested in this pull request are meant to make kmcuda to be compatible on Windows from within VisualStudio 2017 environment. By default - the build fails due to several errors.

See issue #50

Signed-off-by: Aleksandrs Pavlenko pavnexus@gmail.com

@pavlexander
Copy link
Author

My commits were lacking "Signed-off-by" so I added the signature to pull request itself. Unfortunately I couldn't find a way of changing existing comments for commits :) Let me know if this is a no-go and I will re-fork the project and re-apply all the fixes accordingly to DCO with correct comments.

@vmarkovtsev
Copy link
Collaborator

@pavlexander Can you please squash all your commits together - this is preferred in this case.

@pavlexander
Copy link
Author

I must have done something wrong.. Another commit was created automatically, called "Merge branch.." which I was not planning to create! Trying to figure out what went wrong. Maybe I will create another pull request..

pavlexander and others added 4 commits December 10, 2018 15:11
Signed-off-by: pavlexander <pavlexander@gmail.com>
…vlexander/kmcuda into cuda-windows-bugfixes-release

Signed-off-by: pavlexander <pavlexander@gmail.com>
Signed-off-by: Aleksandrs Pavlenko <pavnexus@gmail.com>
Signed-off-by: Aleksandrs Pavlenko <pavnexus@gmail.com>
@pavlexander
Copy link
Author

For some reason when I create a squashed commit, then I am forced to pull previous 22 commits. When that happens, then I am also forced to create an empty "merge" commit, which seems to be failing DCO for some reason, even though it has a sign-off..

@pavlexander
Copy link
Author

Can anyone explain why merge commit from local to remote causes DCO to fail? Even if it has a sign-off?

Sorry, I will be creating a new fork and a new pull request.. Sorry for inconvenience. Still learning git. :)
Seems like it's the best option in this situation.

@vmarkovtsev
Copy link
Collaborator

@ComicAddict
Copy link

Are there any plans to merge this PR?

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.

3 participants