Am 28.01.2010 22:17, schrieb Mike Linck: > Well, even gitk can't show me the information I'm looking for if the > parent branch ended up fast-forwarding to include the changes made in > the topic branch. As far as I can tell there is *no way* to tell what > changes were made in a particular branch after a fast-forward has > taken place, which seems to make it hard to organize fixes for > specific topics/bugs/tickets. You could disable fast forward merges using the --no-ff option. Then git will always create a merge commit even if it could have done a fast forward. This can be enabled permanently for a branch with 'git config branch.master.mergeoptions "--no-ff"'. We use that at my dayjob to preserve the branches after merging. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html