Stephen Bash <b...@genarts.com> writes: > So what is the actual meaning of "Already up-to-date!"? Is it > based on the tree, the reachable commits, or something more > complicated?
The resulting tree of the merge happened to be the same as the original tree (i.e. "git diff HEAD^ HEAD" is empty). This happens quite often and is perfectly normal. After merging topics that has been cooking in 'next' to 'master', merging the resulting 'master' to 'next' is likely to result in that situation, unless 'master' has gained some other changes, such as updating the draft release notes with a commit on it, or applying an obvious and trivial fix before cooking it in 'next'. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
