d860b2e225
GLUT_EXEC_STATE_RUNNING should not have been at the top of the loop, but rather right after glutMainLoopEvent returns, after it processes a single event. As it was, we would be sleeping, waiting for further events even if the user just called glutLeaveMainLoop (which sets ExecState to GLUT_EXEC_STATE_STOP). Also fixed a couple cases if inconsistent use of tabs/spaces for indentation which was causing gcc to emit bogus warnings about misleading indentation around braceless ifs. git-svn-id: https://svn.code.sf.net/p/freeglut/code/trunk@1803 7f0cb862-5218-0410-a997-914c9d46530a |
||
---|---|---|
.github | ||
freeglut | ||
.gitattributes | ||
.gitignore | ||
README.md |
FreeGLUT
This readme file applies to the git clone of FreeGLUT's svn repo on sourceforge.net that is hosted on github. This is provided here to enable user to contribute easier.
Every effort is made to ensure that the git_master
branch only progresses in a fastforward manner, but complete guarantees cannot be given as the sourceforge.net trunk is at all times leading.
I will be unable to merge a pull request if the github clone is behind svn/trunk
on sourceforge.net. Should you detect this, please contact me, maybe through making an issue here on github.
This copy of the svn repository was not created with git svn
but with the excellent svn support of SmartGit.
Notes to self on how to work with this: Basic workflow upon receiving a pull request is as follows:
- Merge pull request on github
- pull in changes to my local clone of the
git_master
branch. - cherry pick the merged commits onto my local clone of the
svn/trunk
branch - push these commits to svn remote (this alters the commits in the local
svn/trunk
clone as extra meta data is added) - merge
svn/trunk
into localgit_master
- push merge commit to github (its fast forward!)