Skip to content
Snippets Groups Projects
Commit 58f1c0db authored by Kyle Brenneman's avatar Kyle Brenneman
Browse files

Merge branch 'copy-mesa-gl-h' into 'master'

Update GL/gl.h to match Mesa.

Closes #194

See merge request !195
parents a1a73db6 5dfdc5a6
No related branches found
No related tags found
Loading
Loading
  • Developer

    @kbrenneman , it looks like GitLab is creating pointless merge commits, cluttering the history. Is there a settings page where you can change it to fast-forward by default?

  • Author Owner

    I think there's a setting for that, but as far as I can tell, it's not just a default. It forces every merge request to be a fast-forward.

    In a lot of cases, the merge commit is useful in and of itself, because it's a place to put a reference to the merge request any discussion attached to it, which could be useful for someone reading back through old commits. A fast-forward merge would lose that.

    For larger things, it also means you can have a series of small commits for easier reading, but treat them as a single unit in the commit history.

    What would be really nice is if GitLab had an option to tell it merge a specific merge request as a fast-forward merge, but the only way I can find to do that is to do it manually.

  • fafryd @fafryd1125

    mentioned in merge request !199 (merged)

    ·

    mentioned in merge request !199 (merged)

    Toggle commit list
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment