X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=Documentation%2Fgit-merge.txt;h=9c08efa53abc2797a7b7ca0e589d83b9a4387987;hb=e18ee576b1420e7b2cfc5c686872fa3b439ac45f;hp=e2954aa76eef46101f38683eb346bd31bf711a40;hpb=17bcdad3b7baa3b12c662663372f1e3cd560dd8e;p=git.git diff --git a/Documentation/git-merge.txt b/Documentation/git-merge.txt index e2954aa76..9c08efa53 100644 --- a/Documentation/git-merge.txt +++ b/Documentation/git-merge.txt @@ -3,15 +3,14 @@ git-merge(1) NAME ---- -git-merge - Grand Unified Merge Driver +git-merge - Join two or more development histories together SYNOPSIS -------- [verse] 'git-merge' [-n] [--no-commit] [--squash] [-s ]... - [--reflog-action=] - -m= ... + [-m ] ... DESCRIPTION ----------- @@ -37,11 +36,6 @@ include::merge-options.txt[] least one . Specifying more than one obviously means you are trying an Octopus. ---reflog-action=:: - This is used internally when `git-pull` calls this command - to record that the merge was created by `pull` command - in the `ref-log` entry that results from the merge. - include::merge-strategies.txt[] @@ -142,7 +136,7 @@ After seeing a conflict, you can do two things: * Resolve the conflicts. `git-diff` would report only the conflicting paths because of the above 2. and 3.. Edit the - working tree files into a desirable shape, `git-update-index` + working tree files into a desirable shape, `git-add` or `git-rm` them, to make the index file contain what the merge result should be, and run `git-commit` to commit the result.