bundle-config.ronn in bundler-1.6.0.rc2

- old
+ new

@@ -84,16 +84,10 @@
 * `without` (`BUNDLE_WITHOUT`):
   A `:`-separated list of groups whose gems bundler should not install
 * `bin` (`BUNDLE_BIN`):
   Install executables from gems in the bundle to the specified directory.
   Defaults to `false`.
-* `gemfile` (`BUNDLE_GEMFILE`):
-  The name of the file that bundler should use as the `Gemfile`. This location
-  of this file also sets the root of the project, which is used to resolve
-  relative paths in the `Gemfile`, among other things. By default, bundler
-  will search up from the current working directory until it finds a
-  `Gemfile`.
 * `ssl_ca_cert` (`BUNDLE_SSL_CA_CERT`):
   Path to a designated CA certificate file or folder containing multiple
   certificates for trusted CAs in PEM format.
 * `ssl_client_cert` (`BUNDLE_SSL_CLIENT_CERT`):
   Path to a designated file containing a X.509 client certificate
@@ -103,9 +97,21 @@
 flag to the [bundle install(1)][bundle-install] command.
 
 You can set them globally either via environment variables or `bundle config`,
 whichever is preferable for your setup. If you use both, environment variables
 will take preference over global settings.
+
+An additional setting is available only as an environment variable:
+
+* `BUNDLE_GEMFILE`:
+  The name of the file that bundler should use as the `Gemfile`. This location
+  of this file also sets the root of the project, which is used to resolve
+  relative paths in the `Gemfile`, among other things. By default, bundler
+  will search up from the current working directory until it finds a
+  `Gemfile`.
+
+Bundler will ignore any `BUNDLE_GEMFILE` entries in local or global
+configuration files.
 
 ## LOCAL GIT REPOS
 
 Bundler also allows you to work against a git repository locally
 instead of using the remote version. This can be achieved by setting