aboutsummaryrefslogtreecommitdiffstats
path: root/DEVELOPMENT.md
diff options
context:
space:
mode:
authorJessica Lynn Suttles <jlsuttles@gmail.com>2013-07-29 12:24:21 -0700
committerJessica Lynn Suttles <jlsuttles@gmail.com>2013-07-29 12:24:21 -0700
commit3057d6cc4fd6182132c9be269da370811e9caea0 (patch)
treec2fb22a09769b61a31af1227cf4b82c7a2304fe1 /DEVELOPMENT.md
parent109b3aa3b5abbccd27cd1f998f384c142d75a1c6 (diff)
downloadbundler-3057d6cc4fd6182132c9be269da370811e9caea0.tar.gz
updates DEVELOPMENT.md dbundle alias to be more general
Diffstat (limited to 'DEVELOPMENT.md')
-rw-r--r--DEVELOPMENT.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
index f1808dfb..443ef0b8 100644
--- a/DEVELOPMENT.md
+++ b/DEVELOPMENT.md
@@ -20,9 +20,9 @@ Bundler doesn't use a Gemfile to list development dependencies, because when we
$ rake spec
- 3. Set up a shell alias to run Bundler from your clone. I use a Bash alias:
+ 3. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias:
- $ alias dbundle='ruby -I ~/src/bundler/bundler/lib ~/src/bundler/bundler/bin/bundle'
+ $ alias dbundle='ruby -I /path/to/bundler/lib /path/to/bundler/bin/bundle'
With that set up, you can test changes you've made to Bundler by running `dbundle`, without interfering with the regular `bundle` command.