Merge branch 'en/fast-import-merge-doc'

Doc update.

* en/fast-import-merge-doc:
git-fast-import.txt: clarify that multiple merge commits are allowed

diff --combined Documentation/git-fast-import.txt
index fad327aecc1b91c0ed48df740c25fd444eb1431b,28b447a3e644066beff4bb77831f97b48b49727f..0bb276269e5e2f9f697f9f965300442591fb353e
--- 1/Documentation/git-fast-import.txt
--- 2/Documentation/git-fast-import.txt
+++ b/Documentation/git-fast-import.txt
@@@ -388,10 -388,9 +388,10 @@@ change to the project
        original-oid?
        ('author' (SP <name>)? SP LT <email> GT SP <when> LF)?
        'committer' (SP <name>)? SP LT <email> GT SP <when> LF
 +      ('encoding' SP <encoding>)?
        data
        ('from' SP <commit-ish> LF)?
-       ('merge' SP <commit-ish> LF)?
+       ('merge' SP <commit-ish> LF)*
        (filemodify | filedelete | filecopy | filerename | filedeleteall | notemodify)*
        LF?
  ....
@@@ -425,7 -424,7 +425,7 @@@ the same commit, as `filedeleteall` wip
  
  The `LF` after the command is optional (it used to be required).  Note
  that for reasons of backward compatibility, if the commit ends with a
 -`data` command (i.e. it has has no `from`, `merge`, `filemodify`,
 +`data` command (i.e. it has no `from`, `merge`, `filemodify`,
  `filedelete`, `filecopy`, `filerename`, `filedeleteall` or
  `notemodify` commands) then two `LF` commands may appear at the end of
  the command instead of just one.
@@@ -456,12 -455,6 +456,12 @@@ that was selected by the --date-format=
  See ``Date Formats'' above for the set of supported formats, and
  their syntax.
  
 +`encoding`
 +^^^^^^^^^^
 +The optional `encoding` command indicates the encoding of the commit
 +message.  Most commits are UTF-8 and the encoding is omitted, but this
 +allows importing commit messages into git without first reencoding them.
 +
  `from`
  ^^^^^^
  The `from` command is used to specify the commit to initialize