On Thu, 28 Jan 2010, Mike Linck wrote: > 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 should consider using tags in conjunction with your bugs/tickets system. The fork point for a bug fix may be tagged, as well as the last commit representing the bugfix completion (not the merge point though). This way you can always retrieve the exact set of commits forming up that bugfix, regardless if it was merged back into the main branch with a fast forward or not. Nicolas -- 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