-
Notifications
You must be signed in to change notification settings - Fork 11
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
Quick survey of git "merge commits" in open source projects #14
Comments
IMHO it is really unfortunate that GitHub doesn't support the rebase / fast-forward merge workflow from the UI :-(. These merge commits don't provide any useful information and are just noise in the history. |
@cdman do the merge commits tell us anything interesting about the way each project is developed? |
Interesting list @lukego. I also wonder the same question: What do the merge commits really tell us? |
@vy: I'll interpret one: The LuaJIT merge commits tell us that upstream is maintaining two branches in parallel: the stable This workflow is supported by Somebody else's turn to interpret the next one :) |
How do different open source projects use Git merge commits? Here is a brief survey: log of the latest 15-or-so merge commits on a few projects/branches. Just a tangential thought following the discussion on snabbco/snabb#725.
Please leave a comment if you have an interesting interpretation :-)
Snabb Switch
Linux kernel
QEMU
V8
(There don't seem to be any merge commits in the v8 repository.)
Rust
OpenStack Nova
Ruby on Rails
LuaJIT (v2.1 branch)
The text was updated successfully, but these errors were encountered: