Commit man pages to source control

This has the benefit that:

* Allows the installation of bundler as a default gem from rubygems to
include man pages.
* Removes the need to build man pages during our tests.
* Makes working with the manifest easier, because we only have source
controlled files, and not a mix of source control and generated files.

To make sure they never fall out of sync, we replace the previous
`man:build` CI task with a `man:check` task that makes sure the
generated man pages are up to date.

1 files changed, 27 insertions, 0 deletions

diff --git a/man/bundle-show.1.txt b/man/bundle-show.1.txt
new file mode 100644
index 0000000000..d22c7d1f22
--- /dev/null
+++ b/man/bundle-show.1.txt
@@ -0,0 +1,27 @@
+BUNDLE-SHOW(1)							BUNDLE-SHOW(1)
+
+
+
+NAME
+       bundle-show - Shows all the gems in your bundle, or the path to a gem
+
+SYNOPSIS
+       bundle show [GEM] [--paths]
+
+DESCRIPTION
+       Without	the [GEM] option, show will print a list of the names and ver-
+       sions of all gems that are required by  your  [Gemfile(5)][Gemfile(5)],
+       sorted by name.
+
+       Calling	show  with  [GEM]  will list the exact location of that gem on
+       your machine.
+
+OPTIONS
+       --paths
+	      List the paths of all gems  that	are  required  by  your  [Gem-
+	      file(5)][Gemfile(5)], sorted by gem name.
+
+
+
+
+				  August 2019			BUNDLE-SHOW(1)