Add missing included files

The architecture of files was reworked. Some include files are missing
now.

Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>

en/cmds-guide.txt

+linkgit:gitattributes[5]::
+	Defining attributes per path.
+
+linkgit:gitcli[7]::
+	Git command-line interface and conventions.
+
+linkgit:gitcore-tutorial[7]::
+	A Git core tutorial for developers.
+
+linkgit:gitcredentials[7]::
+	Providing usernames and passwords to Git.
+
+linkgit:gitcvs-migration[7]::
+	Git for CVS users.
+
+linkgit:gitdiffcore[7]::
+	Tweaking diff output.
+
+linkgit:giteveryday[7]::
+	A useful minimum set of commands for Everyday Git.
+
+linkgit:gitfaq[7]::
+	Frequently asked questions about using Git.
+
+linkgit:gitglossary[7]::
+	A Git Glossary.
+
+linkgit:githooks[5]::
+	Hooks used by Git.
+
+linkgit:gitignore[5]::
+	Specifies intentionally untracked files to ignore.
+
+linkgit:gitmailmap[5]::
+	Map author/committer names and/or E-Mail addresses.
+
+linkgit:gitmodules[5]::
+	Defining submodule properties.
+
+linkgit:gitnamespaces[7]::
+	Git namespaces.
+
+linkgit:gitremote-helpers[7]::
+	Helper programs to interact with remote repositories.
+
+linkgit:gitrepository-layout[5]::
+	Git Repository Layout.
+
+linkgit:gitrevisions[7]::
+	Specifying revisions and ranges for Git.
+
+linkgit:gitsubmodules[7]::
+	Mounting one repository inside another.
+
+linkgit:gittutorial[7]::
+	A tutorial introduction to Git.
+
+linkgit:gittutorial-2[7]::
+	A tutorial introduction to Git: part two.
+
+linkgit:gitworkflows[7]::
+	An overview of recommended workflows with Git.
+

en/line-range-options.txt

+-L<start>,<end>:<file>::
+-L:<funcname>:<file>::
+
+	Trace the evolution of the line range given by '<start>,<end>',
+	or by the function name regex '<funcname>', within the '<file>'. You may
+	not give any pathspec limiters.  This is currently limited to
+	a walk starting from a single revision, i.e., you may only
+	give zero or one positive revision arguments, and
+	'<start>' and '<end>' (or '<funcname>') must exist in the starting revision.
+	You can specify this option more than once. Implies `--patch`.
+	Patch output can be suppressed using `--no-patch`, but other diff formats
+	(namely `--raw`, `--numstat`, `--shortstat`, `--dirstat`, `--summary`,
+	`--name-only`, `--name-status`, `--check`) are not currently implemented.
++
+include::line-range-format.txt[]

en/object-format-disclaimer.txt

+THIS OPTION IS EXPERIMENTAL! SHA-256 support is experimental and still
+in an early stage.  A SHA-256 repository will in general not be able to
+share work with "regular" SHA-1 repositories.  It should be assumed
+that, e.g., Git internal file formats in relation to SHA-256
+repositories may change in backwards-incompatible ways.  Only use
+`--object-format=sha256` for testing purposes.

en/ref-reachability-filters.txt

+When combining multiple `--contains` and `--no-contains` filters, only
+references that contain at least one of the `--contains` commits and
+contain none of the `--no-contains` commits are shown.
+
+When combining multiple `--merged` and `--no-merged` filters, only
+references that are reachable from at least one of the `--merged`
+commits and from none of the `--no-merged` commits are shown.

en/rev-list-description.txt

+List commits that are reachable by following the `parent` links from the
+given commit(s), but exclude commits that are reachable from the one(s)
+given with a '{caret}' in front of them.  The output is given in reverse
+chronological order by default.
+
+You can think of this as a set operation. Commits reachable from any of
+the commits given on the command line form a set, and then commits reachable
+from any of the ones given with '{caret}' in front are subtracted from that
+set.  The remaining commits are what comes out in the command's output.
+Various other options and paths parameters can be used to further limit the
+result.
+
+Thus, the following command:
+
+ifdef::git-rev-list[]
+-----------------------------------------------------------------------
+$ git rev-list foo bar ^baz
+-----------------------------------------------------------------------
+endif::git-rev-list[]
+ifdef::git-log[]
+-----------------------------------------------------------------------
+$ git log foo bar ^baz
+-----------------------------------------------------------------------
+endif::git-log[]
+
+means "list all the commits which are reachable from 'foo' or 'bar', but
+not from 'baz'".
+
+A special notation "'<commit1>'..'<commit2>'" can be used as a
+short-hand for "^'<commit1>' '<commit2>'". For example, either of
+the following may be used interchangeably:
+
+ifdef::git-rev-list[]
+-----------------------------------------------------------------------
+$ git rev-list origin..HEAD
+$ git rev-list HEAD ^origin
+-----------------------------------------------------------------------
+endif::git-rev-list[]
+ifdef::git-log[]
+-----------------------------------------------------------------------
+$ git log origin..HEAD
+$ git log HEAD ^origin
+-----------------------------------------------------------------------
+endif::git-log[]
+
+Another special notation is "'<commit1>'...'<commit2>'" which is useful
+for merges.  The resulting set of commits is the symmetric difference
+between the two operands.  The following two commands are equivalent:
+
+ifdef::git-rev-list[]
+-----------------------------------------------------------------------
+$ git rev-list A B --not $(git merge-base --all A B)
+$ git rev-list A...B
+-----------------------------------------------------------------------
+endif::git-rev-list[]
+ifdef::git-log[]
+-----------------------------------------------------------------------
+$ git log A B --not $(git merge-base --all A B)
+$ git log A...B
+-----------------------------------------------------------------------
+endif::git-log[]

en/signoff-option.txt

+ifdef::git-commit[]
+-s::
+endif::git-commit[]
+--signoff::
+--no-signoff::
+	Add a `Signed-off-by` trailer by the committer at the end of the commit
+	log message.  The meaning of a signoff depends on the project
+	to which you're committing.  For example, it may certify that
+	the committer has the rights to submit the work under the
+	project's license or agrees to some contributor representation,
+	such as a Developer Certificate of Origin.
+	(See http://developercertificate.org for the one used by the
+	Linux kernel and Git projects.)  Consult the documentation or
+	leadership of the project to which you're contributing to
+	understand how the signoffs are used in that project.
++
+The --no-signoff option can be used to countermand an earlier --signoff
+option on the command line.