-
Notifications
You must be signed in to change notification settings - Fork 28
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
gemvertexbuffer_shader #57
Conversation
thanks this is much better. for the future: rather than annotating each commit here in the pull-request, it would be better to do that within the commit.
you should probably use this commit message:
(and possibly also mention which "sourceforge code" you are referring to. but keep this in mind for your next pull request :-) |
yup - realized that commenting each commit was bad practice - but too late i don't mind redoing this one more time editing the file gradually for commits here on github would be very quick to do actually - but then there would be the encoding umlaeute issue again at the top of the cpp - would there be a way to avoid that? |
don't worry this time |
thanks for the help
ending up doing this via command-line entirely - not such a bad thing to know how to do it seems