Remove mentions to bundler history in docs

I don't think we need to keep this information in our docs. Users should
read docs for the version they're using and the history of bundler
distract her from the point of the docs, in my opinion.

3 files changed, 35 insertions, 36 deletions

diff --git a/man/bundle-package.1 b/man/bundle-package.1
index 812d864413..10231d7ad1 100644
--- a/man/bundle-package.1
+++ b/man/bundle-package.1
@@ -13,10 +13,10 @@
 Copy all of the \fB\.gem\fR files needed to run the application into the \fBvendor/cache\fR directory\. In the future, when running [bundle install(1)][bundle\-install], use the gems in the cache in preference to the ones on \fBrubygems\.org\fR\.
 .
 .SH "GIT AND PATH GEMS"
-Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR and \fB:path\fR dependencies besides \.gem files\. This needs to be explicitly enabled via the \fB\-\-all\fR option\. Once used, the \fB\-\-all\fR option will be remembered\.
+The \fBbundle package\fR command can also package \fB:git\fR and \fB:path\fR dependencies besides \.gem files\. This needs to be explicitly enabled via the \fB\-\-all\fR option\. Once used, the \fB\-\-all\fR option will be remembered\.
 .
 .SH "SUPPORT FOR MULTIPLE PLATFORMS"
-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\.
+When using gems that have different packages for different platforms, Bundler supports 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 \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle package(1) \fIbundle\-package\.1\.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\.
diff --git a/man/bundle-package.1.txt b/man/bundle-package.1.txt
index 8ca92b8b6b..707bec3cd6 100644
--- a/man/bundle-package.1.txt
+++ b/man/bundle-package.1.txt
@@ -15,21 +15,20 @@ DESCRIPTION
        the ones on rubygems.org.
 
 GIT AND PATH GEMS
-       Since Bundler 1.2, the bundle package command can also package :git and
-       :path  dependencies  besides  .gem  files.  This needs to be explicitly
-       enabled via the --all option. Once  used,  the  --all  option  will  be
-       remembered.
+       The bundle package command can also package :git and :path dependencies
+       besides	.gem  files. This needs to be explicitly enabled via the --all
+       option. Once used, the --all option will be remembered.
 
 SUPPORT FOR MULTIPLE PLATFORMS
-       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 ven-
-       dor/cache. This needs to be enabled  via  the  --all-platforms  option.
-       This setting will be remembered in your local bundler configuration.
+       When using gems that have different packages for  different  platforms,
+       Bundler	supports caching of gems for other platforms where the Gemfile
+       has been resolved (i.e. present in the lockfile) in vendor/cache.  This
+       needs  to  be enabled via the --all-platforms option. This setting will
+       be remembered in your local bundler configuration.
 
 REMOTE FETCHING
-       By  default, if you run bundle install(1)](bundle-install.1.html) after
-       running bundle package(1)  bundle-package.1.html,  bundler  will  still
+       By default, if you run bundle install(1)](bundle-install.1.html)  after
+       running	bundle	package(1)  bundle-package.1.html,  bundler will still
        connect to rubygems.org to check whether a platform-specific gem exists
        for any of the gems in vendor/cache.
 
@@ -43,35 +42,35 @@ REMOTE FETCHING
 
 
 
-       If you run bundle package under C Ruby, bundler will retrieve the  ver-
-       sion  of  nokogiri  for the "ruby" platform. If you deploy to JRuby and
-       run bundle install, bundler is forced to check to see whether a	"java"
+       If  you run bundle package under C Ruby, bundler will retrieve the ver-
+       sion of nokogiri for the "ruby" platform. If you deploy	to  JRuby  and
+       run  bundle install, bundler is forced to check to see whether a "java"
        platformed nokogiri exists.
 
-       Even  though  the  nokogiri  gem  for  the Ruby platform is technically
-       acceptable on JRuby, it has a C extension that does not run  on	JRuby.
+       Even though the nokogiri gem  for  the  Ruby  platform  is  technically
+       acceptable  on  JRuby, it has a C extension that does not run on JRuby.
        As a result, bundler will, by default, still connect to rubygems.org to
-       check whether it has a version of one of your  gems  more  specific  to
+       check  whether  it  has	a version of one of your gems more specific to
        your platform.
 
-       This  problem  is  also	not  limited to the "java" platform. A similar
+       This problem is also not limited to  the  "java"  platform.  A  similar
        (common) problem can happen when developing on Windows and deploying to
        Linux, or even when developing on OSX and deploying to Linux.
 
-       If  you know for sure that the gems packaged in vendor/cache are appro-
-       priate for the platform you are on, you can run bundle install  --local
-       to  skip  checking  for more appropriate gems, and use the ones in ven-
+       If you know for sure that the gems packaged in vendor/cache are	appro-
+       priate  for the platform you are on, you can run bundle install --local
+       to skip checking for more appropriate gems, and use the	ones  in  ven-
        dor/cache.
 
-       One way to be sure that you have the right platformed versions  of  all
+       One  way  to be sure that you have the right platformed versions of all
        your gems is to run bundle package on an identical machine and check in
-       the gems. For instance, you can run  bundle  package  on  an  identical
-       staging	box during your staging process, and check in the vendor/cache
+       the  gems.  For	instance,  you	can run bundle package on an identical
+       staging box during your staging process, and check in the  vendor/cache
        before deploying to production.
 
-       By default, bundle package(1) bundle-package.1.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,
+       By  default,  bundle  package(1) bundle-package.1.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.
 
 
diff --git a/man/bundle-package.ronn b/man/bundle-package.ronn
index bc137374da..ad745f8491 100644
--- a/man/bundle-package.ronn
+++ b/man/bundle-package.ronn
@@ -13,17 +13,17 @@ use the gems in the cache in preference to the ones on `rubygems.org`.
 
 ## GIT AND PATH GEMS
 
-Since Bundler 1.2, the `bundle package` command can also package `:git` and
-`:path` dependencies besides .gem files. This needs to be explicitly enabled
-via the `--all` option. Once used, the `--all` option will be remembered.
+The `bundle package` command can also package `:git` and `:path` dependencies
+besides .gem files. This needs to be explicitly enabled via the `--all` option.
+Once used, the `--all` option will be remembered.
 
 ## SUPPORT FOR MULTIPLE PLATFORMS
 
 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 `vendor/cache`.  This needs
-to be enabled via the `--all-platforms` option. This setting will be remembered
-in your local bundler configuration.
+supports caching of gems for other platforms where the Gemfile has been resolved
+(i.e. present in the lockfile) in `vendor/cache`.  This needs to be enabled via
+the `--all-platforms` option. This setting will be remembered in your local
+bundler configuration.
 
 ## REMOTE FETCHING