Switch branches/tags
Commits on Aug 30, 2012
  1. Revert "Ruby 2.0 (trunk ruby) is not Ruby 1.9"

    indirect authored and hone committed Aug 16, 2012
    As discussed in #1539 and #2056, Bundler uses platforms to distinguish Ruby ABI versions. That means the known (and ATM supported) use cases for the ruby_19 platform include Ruby 2.0.
    This reverts commit dcfb640.
  2. fix whitespace test

    hone committed Aug 30, 2012
  3. Version 1.2.0

    hone committed Aug 30, 2012
  4. update changelog for 1.2.0

    hone committed Aug 30, 2012
  5. bundle platform man pages

    hone committed Aug 30, 2012
Commits on Aug 25, 2012
  1. Fix #2075. Return to old namespace behavior.

    hone committed Aug 25, 2012
    $1 gets overidden by gsub.
Commits on Aug 14, 2012
  1. fix test case names

    hone committed Aug 14, 2012
Commits on Aug 9, 2012
Commits on Aug 7, 2012
  1. Merge pull request #1931 from coding46/patch-1

    radar committed Aug 7, 2012
    Simple Typo
Commits on Jul 18, 2012
Commits on Jul 17, 2012
  1. Version 1.2.0.rc with changelog

    hone committed Jul 17, 2012
  2. don't need these tests in 1.2

    hone committed Jul 17, 2012
  3. Merge branch '1-1-stable'

    hone committed Jul 17, 2012
  4. Version 1.1.5 with changelog

    hone committed Jul 17, 2012
  5. special case `ruby` directive

    hone committed Jul 17, 2012
    This is light of the upcoming 1.2.0 release which adds this feature.
    This way people still using 1.1.x can run 1.2.0 Gemfiles that employ
    this feature and get a notification about upgrading.
  6. rename --no-lock to --dry-run

    hone committed Jul 17, 2012
  7. Make locking the Gemfile optional on $ bundle check

    Sven Fuchs authored and hone committed Apr 1, 2012
    Currently `bundle check` locks the Gemfile. According to @indirect this
    behaviour is intentional (see!/indirect/status/186493694013210624).
    I am working on a CLI monitoring tool that makes it easier to work with
    cross-repository changes on projects that are split up into several
    This tool is supposed to display status information such as out-of-date
    bundler Gemfiles etc. To do so it watches the filesystem and queries for
    information on demand. Using `bundle check` to do so currently leads to
    highly confusing side-effects because suddenly the git working directory
    might be dirty - having changed the Gemfile.lock - because `bundle
    check` has been run in the background.
    This patch adds a boolean method option `--[no-]lock` to `bundle check`
    that defaults to `true` in order to not change the current behaviour but
    make it possible for users to turn it off.
    Sidenote: apparently the same behaviour also applies to `bundle show`.
    Am I the only one who finds this highly confusing?
  8. remove unnecessary '|| nil'

    hone committed Jul 17, 2012
  9. Prune git and path directories inside vendor/cache, closes #1988

    josevalim committed Jul 17, 2012
    From this commit on, we add a .bundlecache file inside
    each git/path directory in vendor/cache so we know it
    came from bundler. This allow us to delete those specific
    directories without messing with user's specific ones.
Commits on Jul 13, 2012
  1. loosen ruby directive for engines

    hone committed Jul 13, 2012
    allow other engines to qualify when the engine is omitted. So, in the
    ruby "1.9.3"
    will work with JRuby and RBX as long as the RUBY_VERSION matches
Commits on Jul 5, 2012
  1. Check for nil PATH

    indirect committed Jul 5, 2012
    fixes #2006
Commits on Jun 22, 2012
  1. Merge pull request #1998 from postmodern/patch-1

    radar committed Jun 22, 2012
    Fixed typo. $/ and NOT $\
  2. Merge pull request #2001 from postmodern/txt

    radar committed Jun 22, 2012
Commits on Jun 21, 2012
Commits on Jun 15, 2012
Commits on Jun 14, 2012
  1. kill the stray space

    indirect committed Jun 14, 2012