bundler 1.16.1 → 1.16.2

data/man/bundle-inject.1.txt

@@ -10,10 +10,10 @@ SYNOPSIS
 
 DESCRIPTION
        Adds  the  named gem(s) with their version requirements to the resolved
-       Gemfile(5).
+       [Gemfile(5)][Gemfile(5)].
 
-       This command will add the gem to both your Gemfile(5) and  Gemfile.lock
-       if it isn't listed yet.
+       This command will add the gem to both your [Gemfile(5)][Gemfile(5)] and
+       Gemfile.lock if it isn't listed yet.
 
        Example:
 
@@ -25,8 +25,8 @@ DESCRIPTION
 
 
        This  will  inject the 'rack' gem with a version greater than 0 in your
-       Gemfile(5) and Gemfile.lock
+       [Gemfile(5)][Gemfile(5)] and Gemfile.lock
 
 
 
-				 February 2017		      BUNDLE-INJECT(1)
+				 February 2018		      BUNDLE-INJECT(1)

data/man/bundle-inject.ronn

@@ -8,9 +8,9 @@ bundle-inject(1) -- Add named gem(s) with version requirements to Gemfile
 ## DESCRIPTION
 
 Adds the named gem(s) with their version requirements to the resolved
-`Gemfile(5)`.
+[`Gemfile(5)`][Gemfile(5)].
 
-This command will add the gem to both your `Gemfile(5)` and Gemfile.lock if it
+This command will add the gem to both your [`Gemfile(5)`][Gemfile(5)] and Gemfile.lock if it
 isn't listed yet.
 
 Example:
@@ -19,4 +19,4 @@ Example:
     bundle inject 'rack' '> 0'
 
 This will inject the 'rack' gem with a version greater than 0 in your
-`Gemfile(5)` and Gemfile.lock
+[`Gemfile(5)`][Gemfile(5)] and Gemfile.lock

data/man/bundle-install.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INSTALL" "1" "December 2017" "" ""
+.TH "BUNDLE\-INSTALL" "1" "May 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-install\fR \- Install the dependencies specified in your Gemfile
@@ -291,7 +291,7 @@ Even though \fBactivemerchant\fR declares a very loose dependency that theoretic
 To explicitly update \fBactionpack\fR, including its dependencies which other gems in the Gemfile(5) still depend on, run \fBbundle update actionpack\fR (see \fBbundle update(1)\fR)\.
 .
 .P
-\fBSummary\fR: In general, after making a change to the Gemfile(5) , you should first try to run \fBbundle install\fR, which will guarantee that no other gem in the Gemfile(5) is impacted by the change\. If that does not work, run [bundle update(1)][bundle\-update]\.
+\fBSummary\fR: In general, after making a change to the Gemfile(5) , you should first try to run \fBbundle install\fR, which will guarantee that no other gem in the Gemfile(5) is impacted by the change\. If that does not work, run [bundle update(1)][bundle\-update(1)]\.
 .
 .SH "SEE ALSO"
 .

data/man/bundle-install.1.txt

@@ -369,7 +369,7 @@ CONSERVATIVE UPDATING
        Summary:  In  general,  after  making  a change to the Gemfile(5) , you
        should first try to run bundle install, which will  guarantee  that  no
        other gem in the Gemfile(5) is impacted by the change. If that does not
-       work, run [bundle update(1)][bundle-update].
+       work, run [bundle update(1)][bundle-update(1)].
 
 SEE ALSO
        o   Gem				install 			  docs
@@ -382,4 +382,4 @@ SEE ALSO
 
 
 
-				 December 2017		     BUNDLE-INSTALL(1)
+				   May 2018		     BUNDLE-INSTALL(1)

data/man/bundle-install.ronn

@@ -361,7 +361,7 @@ which other gems in the Gemfile(5) still depend on, run
 `Summary`: In general, after making a change to the Gemfile(5) , you
 should first try to run `bundle install`, which will guarantee that no
 other gem in the Gemfile(5) is impacted by the change. If that
-does not work, run [bundle update(1)][bundle-update].
+does not work, run [bundle update(1)][bundle-update(1)].
 
 ## SEE ALSO
 

data/man/bundle-list.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LIST" "1" "August 2017" "" ""
+.TH "BUNDLE\-LIST" "1" "May 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-list\fR \- List all the gems in the bundle

data/man/bundle-list.1.txt

@@ -18,4 +18,4 @@ OPTIONS
 
 
 
-				  August 2017			BUNDLE-LIST(1)
+				   May 2018			BUNDLE-LIST(1)

data/man/bundle-lock.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LOCK" "1" "February 2017" "" ""
+.TH "BUNDLE\-LOCK" "1" "February 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-lock\fR \- Creates / Updates a lockfile without installing
@@ -81,4 +81,4 @@ If you want your bundle to support platforms other than the one you\'re running
 For a full explanation of gem platforms, see \fBgem help platform\fR\.
 .
 .SH "PATCH LEVEL OPTIONS"
-See [bundle update(1)][bundle\-update] for details\.
+See [bundle update(1)][bundle\-update(1)] for details\.

data/man/bundle-lock.1.txt

@@ -86,8 +86,8 @@ SUPPORTING OTHER PLATFORMS
        For a full explanation of gem platforms, see gem help platform.
 
 PATCH LEVEL OPTIONS
-       See [bundle update(1)][bundle-update] for details.
+       See [bundle update(1)][bundle-update(1)] for details.
 
 
 
-				 February 2017			BUNDLE-LOCK(1)
+				 February 2018			BUNDLE-LOCK(1)

data/man/bundle-lock.ronn

@@ -91,4 +91,4 @@ For a full explanation of gem platforms, see `gem help platform`.
 
 ## PATCH LEVEL OPTIONS
 
-See [bundle update(1)][bundle-update] for details.
+See [bundle update(1)][bundle-update(1)] for details.

data/man/bundle-outdated.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OUTDATED" "1" "July 2017" "" ""
+.TH "BUNDLE\-OUTDATED" "1" "February 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-outdated\fR \- List installed gems with newer versions available
@@ -71,7 +71,7 @@ Only list minor newer versions\.
 Only list patch newer versions\.
 .
 .SH "PATCH LEVEL OPTIONS"
-See [bundle update(1)][bundle\-update] for details\.
+See [bundle update(1)][bundle\-update(1)] for details\.
 .
 .P
 One difference between the patch level options in \fBbundle update\fR and here is the \fB\-\-strict\fR option\. \fB\-\-strict\fR was already an option on outdated before the patch level options were added\. \fB\-\-strict\fR wasn\'t altered, and the \fB\-\-update\-strict\fR option on \fBoutdated\fR reflects what \fB\-\-strict\fR does on \fBbundle update\fR\.

data/man/bundle-outdated.1.txt

@@ -63,7 +63,7 @@ OPTIONS
 	      Only list patch newer versions.
 
 PATCH LEVEL OPTIONS
-       See [bundle update(1)][bundle-update] for details.
+       See [bundle update(1)][bundle-update(1)] for details.
 
        One difference between the patch level options  in  bundle  update  and
        here is the --strict option. --strict was already an option on outdated
@@ -124,4 +124,4 @@ FILTERING OUTPUT
 
 
 
-				   July 2017		    BUNDLE-OUTDATED(1)
+				 February 2018		    BUNDLE-OUTDATED(1)

data/man/bundle-outdated.ronn

@@ -69,7 +69,7 @@ are up to date, Bundler will exit with a status of 0. Otherwise, it will exit 1.
 
 ## PATCH LEVEL OPTIONS
 
-See [bundle update(1)][bundle-update] for details.
+See [bundle update(1)][bundle-update(1)] for details.
 
 One difference between the patch level options in `bundle update` and here is the `--strict` option.
 `--strict` was already an option on outdated before the patch level options were added. `--strict`

data/man/bundle-package.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PACKAGE" "1" "September 2017" "" ""
+.TH "BUNDLE\-PACKAGE" "1" "February 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application
@@ -19,7 +19,7 @@ Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR
 When using gems that have different packages for different platforms, Bundler 1\.8 and newer support caching of gems for other platforms where the Gemfile has been resolved (i\.e\. present in the lockfile) in \fBvendor/cache\fR\. This needs to be enabled via the \fB\-\-all\-platforms\fR option\. This setting will be remembered in your local bundler configuration\.
 .
 .SH "REMOTE FETCHING"
-By default, if you run [bundle install(1)][bundle\-install] after running [bundle package(1)][bundle\-package], bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
+By default, if you run \fBbundle install(1)\fR][bundle\-install(1)] after running bundle package(1) \fIbundle\-package\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
 .
 .P
 For instance, consider this Gemfile(5):
@@ -52,4 +52,4 @@ If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriat
 One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle package\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle package\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\.
 .
 .P
-By default, [bundle package(1)][bundle\-package] fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.
+By default, bundle package(1) \fIbundle\-package\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.

data/man/bundle-package.1.txt

@@ -28,10 +28,10 @@ SUPPORT FOR MULTIPLE PLATFORMS
        This setting will be remembered in your local bundler configuration.
 
 REMOTE FETCHING
-       By  default,  if you run [bundle install(1)][bundle-install] after run-
-       ning [bundle package(1)][bundle-package], bundler will still connect to
-       rubygems.org to check whether a platform-specific gem exists for any of
-       the gems in vendor/cache.
+       By default, if you run bundle install(1)][bundle-install(1)] after run-
+       ning bundle package(1) bundle-package.html, bundler will still  connect
+       to rubygems.org to check whether a platform-specific gem exists for any
+       of the gems in vendor/cache.
 
        For instance, consider this Gemfile(5):
 
@@ -69,11 +69,11 @@ REMOTE FETCHING
        staging	box during your staging process, and check in the vendor/cache
        before deploying to production.
 
-       By  default,  [bundle  package(1)][bundle-package]  fetches  and   also
+       By default, bundle  package(1)  bundle-package.html  fetches  and  also
        installs  the gems to the default location. To package the dependencies
        to vendor/cache without installing them to the local install  location,
        you can run bundle package --no-install.
 
 
 
-				September 2017		     BUNDLE-PACKAGE(1)
+				 February 2018		     BUNDLE-PACKAGE(1)

data/man/bundle-package.ronn

@@ -27,8 +27,8 @@ in your local bundler configuration.
 
 ## REMOTE FETCHING
 
-By default, if you run [bundle install(1)][bundle-install] after running
-[bundle package(1)][bundle-package], bundler will still connect to `rubygems.org`
+By default, if you run `bundle install(1)`][bundle-install(1)] after running
+[bundle package(1)][bundle-package(1)], bundler will still connect to `rubygems.org`
 to check whether a platform-specific gem exists for any of the gems
 in `vendor/cache`.
 
@@ -66,7 +66,7 @@ machine and check in the gems. For instance, you can run
 staging process, and check in the `vendor/cache` before
 deploying to production.
 
-By default, [bundle package(1)][bundle-package] fetches and also
+By default, [bundle package(1)][bundle-package(1)] fetches and also
 installs the gems to the default location. To package the
 dependencies to `vendor/cache` without installing them to the
 local install location, you can run `bundle package --no-install`.

data/man/bundle-pristine.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PRISTINE" "1" "August 2017" "" ""
+.TH "BUNDLE\-PRISTINE" "1" "January 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition

data/man/bundle-pristine.1.txt

@@ -41,4 +41,4 @@ DESCRIPTION
 
 
 
-				  August 2017		    BUNDLE-PRISTINE(1)
+				 January 2018		    BUNDLE-PRISTINE(1)

data/man/bundle-show.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-SHOW" "1" "February 2017" "" ""
+.TH "BUNDLE\-SHOW" "1" "February 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem
@@ -10,7 +10,7 @@
 \fBbundle show\fR [GEM] [\-\-paths]
 .
 .SH "DESCRIPTION"
-Without the [GEM] option, \fBshow\fR will print a list of the names and versions of all gems that are required by your \fBGemfile(5)\fR\.
+Without the [GEM] option, \fBshow\fR will print a list of the names and versions of all gems that are required by your [\fBGemfile(5)\fR][Gemfile(5)]\.
 .
 .P
 Calling show with [GEM] will list the exact location of that gem on your machine\.
@@ -19,5 +19,5 @@ Calling show with [GEM] will list the exact location of that gem on your machine
 .
 .TP
 \fB\-\-paths\fR
-List the paths of all gems that are required by your \fBGemfile(5)\fR\.
+List the paths of all gems that are required by your [\fBGemfile(5)\fR][Gemfile(5)]\.
 

data/man/bundle-show.1.txt

@@ -10,16 +10,17 @@ SYNOPSIS
 
 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).
+       sions of all gems that are required by your [Gemfile(5)][Gemfile(5)].
 
        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 Gemfile(5).
+	      List  the  paths	of  all  gems  that are required by your [Gem-
+	      file(5)][Gemfile(5)].
 
 
 
 
-				 February 2017			BUNDLE-SHOW(1)
+				 February 2018			BUNDLE-SHOW(1)

data/man/bundle-show.ronn

@@ -9,7 +9,7 @@ bundle-show(1) -- Shows all the gems in your bundle, or the path to a gem
 ## DESCRIPTION
 
 Without the [GEM] option, `show` will print a list of the names and versions of
-all gems that are required by your `Gemfile(5)`.
+all gems that are required by your [`Gemfile(5)`][Gemfile(5)].
 
 Calling show with [GEM] will list the exact location of that gem on your
 machine.
@@ -17,4 +17,4 @@ machine.
 ## OPTIONS
 
 * `--paths`:
-  List the paths of all gems that are required by your `Gemfile(5)`.
+  List the paths of all gems that are required by your [`Gemfile(5)`][Gemfile(5)].

data/man/bundle-update.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-UPDATE" "1" "July 2017" "" ""
+.TH "BUNDLE\-UPDATE" "1" "May 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-update\fR \- Update your gems to the latest available versions
@@ -10,7 +10,7 @@
 \fBbundle update\fR \fI*gems\fR [\-\-group=NAME] [\-\-source=NAME] [\-\-local] [\-\-ruby] [\-\-bundler[=VERSION]] [\-\-full\-index] [\-\-jobs=JOBS] [\-\-quiet] [\-\-force] [\-\-patch|\-\-minor|\-\-major] [\-\-strict] [\-\-conservative]
 .
 .SH "DESCRIPTION"
-Update the gems specified (all gems, if none are specified), ignoring the previously installed gems specified in the \fBGemfile\.lock\fR\. In general, you should use [bundle install(1)][bundle\-install] to install the same exact gems and versions across machines\.
+Update the gems specified (all gems, if none are specified), ignoring the previously installed gems specified in the \fBGemfile\.lock\fR\. In general, you should use [bundle install(1)][bundle\-install(1)] to install the same exact gems and versions across machines\.
 .
 .P
 You would use \fBbundle update\fR to explicitly update the version of a gem\.
@@ -97,7 +97,7 @@ gem "nokogiri"
 .IP "" 0
 .
 .P
-When you run [bundle install(1)][bundle\-install] the first time, bundler will resolve all of the dependencies, all the way down, and install what you need:
+When you run [bundle install(1)][bundle\-install(1)] the first time, bundler will resolve all of the dependencies, all the way down, and install what you need:
 .
 .IP "" 4
 .
@@ -140,10 +140,10 @@ Use `bundle show [gemname]` to see where a bundled gem is installed\.
 .IP "" 0
 .
 .P
-As you can see, even though you have two gems in the Gemfile(5), your application needs 26 different gems in order to run\. Bundler remembers the exact versions it installed in \fBGemfile\.lock\fR\. The next time you run [bundle install(1)][bundle\-install], bundler skips the dependency resolution and installs the same gems as it installed last time\.
+As you can see, even though you have two gems in the Gemfile(5), your application needs 26 different gems in order to run\. Bundler remembers the exact versions it installed in \fBGemfile\.lock\fR\. The next time you run [bundle install(1)][bundle\-install(1)], bundler skips the dependency resolution and installs the same gems as it installed last time\.
 .
 .P
-After checking in the \fBGemfile\.lock\fR into version control and cloning it on another machine, running [bundle install(1)][bundle\-install] will \fIstill\fR install the gems that you installed last time\. You don\'t need to worry that a new release of \fBerubis\fR or \fBmail\fR changes the gems you use\.
+After checking in the \fBGemfile\.lock\fR into version control and cloning it on another machine, running [bundle install(1)][bundle\-install(1)] will \fIstill\fR install the gems that you installed last time\. You don\'t need to worry that a new release of \fBerubis\fR or \fBmail\fR changes the gems you use\.
 .
 .P
 However, from time to time, you might want to update the gems you are using to the newest versions that still match the gems in your Gemfile(5)\.
@@ -204,10 +204,10 @@ In this case, the two gems have their own set of dependencies, but they share \f
 In short, by default, when you update a gem using \fBbundle update\fR, bundler will update all dependencies of that gem, including those that are also dependencies of another gem\.
 .
 .P
-To prevent updating shared dependencies, prior to version 1\.14 the only option was the \fBCONSERVATIVE UPDATING\fR behavior in [bundle install(1)][bundle\-install]:
+To prevent updating shared dependencies, prior to version 1\.14 the only option was the \fBCONSERVATIVE UPDATING\fR behavior in [bundle install(1)][bundle\-install(1)]:
 .
 .P
-In this scenario, updating the \fBthin\fR version manually in the Gemfile(5), and then running [bundle install(1)][bundle\-install] will only update \fBdaemons\fR and \fBeventmachine\fR, but not \fBrack\fR\. For more information, see the \fBCONSERVATIVE UPDATING\fR section of [bundle install(1)][bundle\-install]\.
+In this scenario, updating the \fBthin\fR version manually in the Gemfile(5), and then running [bundle install(1)][bundle\-install(1)] will only update \fBdaemons\fR and \fBeventmachine\fR, but not \fBrack\fR\. For more information, see the \fBCONSERVATIVE UPDATING\fR section of [bundle install(1)][bundle\-install(1)]\.
 .
 .P
 Starting with 1\.14, specifying the \fB\-\-conservative\fR option will also prevent shared dependencies from being updated\.
@@ -375,7 +375,7 @@ Make sure to check the updated \fBGemfile\.lock\fR into version control
 $ git add Gemfile\.lock
 .
 .IP "\(bu" 4
-If [bundle install(1)][bundle\-install] reports a conflict, manually update the specific gems that you changed in the Gemfile(5)
+If [bundle install(1)][bundle\-install(1)] reports a conflict, manually update the specific gems that you changed in the Gemfile(5)
 .
 .IP
 $ bundle update rails thin

data/man/bundle-update.1.txt

@@ -13,8 +13,8 @@ SYNOPSIS
 DESCRIPTION
        Update  the  gems specified (all gems, if none are specified), ignoring
        the previously installed gems specified in the  Gemfile.lock.  In  gen-
-       eral, you should use [bundle install(1)][bundle-install] to install the
-       same exact gems and versions across machines.
+       eral,  you should use [bundle install(1)][bundle-install(1)] to install
+       the same exact gems and versions across machines.
 
        You would use bundle update to explicitly update the version of a  gem.
 
@@ -91,7 +91,7 @@ UPDATING ALL GEMS
 
 
 
-       When  you  run  [bundle	install(1)][bundle-install]  the  first  time,
+       When you run [bundle  install(1)][bundle-install(1)]  the  first  time,
        bundler	will  resolve  all  of the dependencies, all the way down, and
        install what you need:
 
@@ -134,11 +134,11 @@ UPDATING ALL GEMS
        As you can see, even though you have two gems in the  Gemfile(5),  your
        application  needs 26 different gems in order to run. Bundler remembers
        the exact versions it installed in Gemfile.lock. The next time you  run
-       [bundle install(1)][bundle-install], bundler skips the dependency reso-
-       lution and installs the same gems as it installed last time.
+       [bundle	install(1)][bundle-install(1)],  bundler  skips the dependency
+       resolution and installs the same gems as it installed last time.
 
        After checking in the Gemfile.lock into version control and cloning  it
-       on  another  machine,  running [bundle install(1)][bundle-install] will
+       on another machine, running [bundle install(1)][bundle-install(1)] will
        still install the gems that you installed last time. You don't need  to
        worry that a new release of erubis or mail changes the gems you use.
 
@@ -208,19 +208,20 @@ OVERLAPPING DEPENDENCIES
 
        To prevent updating shared dependencies, prior to version 1.14 the only
        option	 was   the   CONSERVATIVE   UPDATING   behavior   in   [bundle
-       install(1)][bundle-install]:
+       install(1)][bundle-install(1)]:
 
        In this scenario, updating the thin version manually in the Gemfile(5),
-       and  then  running [bundle install(1)][bundle-install] will only update
-       daemons and eventmachine, but not rack. For more information,  see  the
-       CONSERVATIVE UPDATING section of [bundle install(1)][bundle-install].
+       and  then  running  [bundle  install(1)][bundle-install(1)]  will  only
+       update daemons and eventmachine, but not rack.  For  more  information,
+       see  the  CONSERVATIVE  UPDATING  section  of  [bundle install(1)][bun-
+       dle-install(1)].
 
        Starting with 1.14, specifying the --conservative option will also pre-
        vent shared dependencies from being updated.
 
 PATCH LEVEL OPTIONS
-       Version 1.14 introduced 4 patch-level options that will	influence  how
-       gem  versions  are  resolved. One of the following options can be used:
+       Version	1.14  introduced 4 patch-level options that will influence how
+       gem versions are resolved. One of the following options	can  be  used:
        --patch, --minor or --major. --strict can be added to further influence
        resolution.
 
@@ -237,41 +238,41 @@ PATCH LEVEL OPTIONS
 	      Do not allow any gem to be updated past latest --patch | --minor
 	      | --major.
 
-       When Bundler is resolving what versions	to  use  to  satisfy  declared
-       requirements  in  the Gemfile or in parent gems, it looks up all avail-
+       When  Bundler  is  resolving  what  versions to use to satisfy declared
+       requirements in the Gemfile or in parent gems, it looks up  all	avail-
        able versions, filters out any versions that don't satisfy the require-
        ment, and then, by default, sorts them from newest to oldest, consider-
        ing them in that order.
 
-       Providing one of the patch level options  (e.g.	--patch)  changes  the
-       sort  order of the satisfying versions, causing Bundler to consider the
+       Providing  one  of  the	patch level options (e.g. --patch) changes the
+       sort order of the satisfying versions, causing Bundler to consider  the
        latest --patch or --minor version available before other versions. Note
        that versions outside the stated patch level could still be resolved to
        if necessary to find a suitable dependency graph.
 
-       For example, if gem 'foo' is locked at 1.0.2, with no  gem  requirement
-       defined	in the Gemfile, and versions 1.0.3, 1.0.4, 1.1.0, 1.1.1, 2.0.0
+       For  example,  if gem 'foo' is locked at 1.0.2, with no gem requirement
+       defined in the Gemfile, and versions 1.0.3, 1.0.4, 1.1.0, 1.1.1,  2.0.0
        all exist, the default order of preference by default (--major) will be
        "2.0.0, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2".
 
-       If  the	--patch option is used, the order of preference will change to
+       If the --patch option is used, the order of preference will  change  to
        "1.0.4, 1.0.3, 1.0.2, 1.1.1, 1.1.0, 2.0.0".
 
-       If the --minor option is used, the order of preference will  change  to
+       If  the	--minor option is used, the order of preference will change to
        "1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 2.0.0".
 
-       Combining  the --strict option with any of the patch level options will
-       remove any versions beyond the scope of	the  patch  level  option,  to
+       Combining the --strict option with any of the patch level options  will
+       remove  any  versions  beyond  the  scope of the patch level option, to
        ensure that no gem is updated that far.
 
-       To  continue the previous example, if both --patch and --strict options
+       To continue the previous example, if both --patch and --strict  options
        are used, the available versions for resolution would be "1.0.4, 1.0.3,
-       1.0.2".	If  --minor  and --strict are used, it would be "1.1.1, 1.1.0,
+       1.0.2". If --minor and --strict are used, it would  be  "1.1.1,	1.1.0,
        1.0.4, 1.0.3, 1.0.2".
 
-       Gem requirements as defined in the Gemfile  will  still	be  the  first
+       Gem  requirements  as  defined  in  the Gemfile will still be the first
        determining factor for what versions are available. If the gem require-
-       ment for foo in the Gemfile is '~> 1.0', that will accomplish the  same
+       ment  for foo in the Gemfile is '~> 1.0', that will accomplish the same
        thing as providing the --minor and --strict options.
 
 PATCH LEVEL EXAMPLES
@@ -320,26 +321,26 @@ PATCH LEVEL EXAMPLES
 
 
 
-       In  case 1, bar is upgraded to 2.1.1, a minor version increase, because
+       In case 1, bar is upgraded to 2.1.1, a minor version increase,  because
        the dependency from foo 1.4.5 required it.
 
-       In case 2, only foo is requested  to  be  unlocked,  but  bar  is  also
-       allowed	to move because it's not a declared dependency in the Gemfile.
+       In  case  2,  only  foo	is  requested  to be unlocked, but bar is also
+       allowed to move because it's not a declared dependency in the  Gemfile.
 
-       In case 3, bar goes up a whole major release, because a minor  increase
-       is  preferred now for foo, and when it goes to 1.5.1, it requires 3.0.0
+       In  case 3, bar goes up a whole major release, because a minor increase
+       is preferred now for foo, and when it goes to 1.5.1, it requires  3.0.0
        of bar.
 
        In case 4, foo is preferred up to a minor version, but 1.5.1 won't work
-       because	the  --strict  flag removes bar 3.0.0 from consideration since
+       because the --strict flag removes bar 3.0.0  from  consideration  since
        it's a major increment.
 
-       In case 5, both foo and bar have any minor or major increments  removed
-       from  consideration  because of the --strict flag, so the most they can
+       In  case 5, both foo and bar have any minor or major increments removed
+       from consideration because of the --strict flag, so the most  they  can
        move is up to 1.4.4 and 2.0.4.
 
 RECOMMENDED WORKFLOW
-       In general, when working with an application managed with bundler,  you
+       In  general, when working with an application managed with bundler, you
        should use the following workflow:
 
        o   After you create your Gemfile(5) for the first time, run
@@ -350,7 +351,7 @@ RECOMMENDED WORKFLOW
 
 	   $ git add Gemfile.lock
 
-       o   When  checking  out this repository on another development machine,
+       o   When checking out this repository on another  development  machine,
 	   run
 
 	   $ bundle install
@@ -359,7 +360,7 @@ RECOMMENDED WORKFLOW
 
 	   $ bundle install --deployment
 
-       o   After changing the Gemfile(5) to reflect a  new  or	update	depen-
+       o   After  changing  the  Gemfile(5)  to reflect a new or update depen-
 	   dency, run
 
 	   $ bundle install
@@ -368,12 +369,12 @@ RECOMMENDED WORKFLOW
 
 	   $ git add Gemfile.lock
 
-       o   If [bundle install(1)][bundle-install] reports a conflict, manually
-	   update the specific gems that you changed in the Gemfile(5)
+       o   If [bundle install(1)][bundle-install(1)] reports a conflict, manu-
+	   ally update the specific gems that you changed in the Gemfile(5)
 
 	   $ bundle update rails thin
 
-       o   If you want to update all the gems to the latest possible  versions
+       o   If  you want to update all the gems to the latest possible versions
 	   that still match the gems listed in the Gemfile(5), run
 
 	   $ bundle update
@@ -383,4 +384,4 @@ RECOMMENDED WORKFLOW
 
 
 
-				   July 2017		      BUNDLE-UPDATE(1)
+				   May 2018		      BUNDLE-UPDATE(1)