The 'git merge' command is generally not used to tie completely independent projects together (though it can be used to do that) but to reconcile branches of development that may have diverged. Try to make this clearer in its one-line description. Cc: Petr Baudis <pasky@xxxxxxx> Cc: Junio C Hamano <gitster@xxxxxxxxx> Cc: Thomas Rast <trast@xxxxxxxxxxxxxxx> Signed-off-by: Jonathan Nieder <jrnieder@xxxxxxxxx> --- I am not sure this is an improvement at all. Mostly I wanted to convey the idea of code forks being reconciled, but the resulting phrase is not nearly as nice. Documentation/git-merge.txt | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/Documentation/git-merge.txt b/Documentation/git-merge.txt index e886c2e..394ad0a 100644 --- a/Documentation/git-merge.txt +++ b/Documentation/git-merge.txt @@ -3,8 +3,7 @@ git-merge(1) NAME ---- -git-merge - Join two or more development histories together - +git-merge - Re-join diverging branches of development SYNOPSIS -------- -- 1.6.6 -- 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