0464a346450437493effa497757582c19bb0a5dd
   1--summary::
   2        Show a diffstat at the end of the merge. The diffstat is also
   3        controlled by the configuration option merge.diffstat.
   4
   5-n, \--no-summary::
   6        Do not show diffstat at the end of the merge.
   7
   8--no-commit::
   9        Perform the merge but pretend the merge failed and do
  10        not autocommit, to give the user a chance to inspect and
  11        further tweak the merge result before committing.
  12
  13--commit::
  14        Perform the merge and commit the result. This option can
  15        be used to override --no-commit.
  16
  17--squash::
  18        Produce the working tree and index state as if a real
  19        merge happened, but do not actually make a commit or
  20        move the `HEAD`, nor record `$GIT_DIR/MERGE_HEAD` to
  21        cause the next `git commit` command to create a merge
  22        commit.  This allows you to create a single commit on
  23        top of the current branch whose effect is the same as
  24        merging another branch (or more in case of an octopus).
  25
  26--no-squash::
  27        Perform the merge and commit the result. This option can
  28        be used to override --squash.
  29
  30-s <strategy>, \--strategy=<strategy>::
  31        Use the given merge strategy; can be supplied more than
  32        once to specify them in the order they should be tried.
  33        If there is no `-s` option, a built-in list of strategies
  34        is used instead (`git-merge-recursive` when merging a single
  35        head, `git-merge-octopus` otherwise).