Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Aug 17, 2011
  1. @vmg @defunkt

    Properly print time offsets

    vmg committed with defunkt
Commits on Jul 10, 2011
  1. @rtomayko

    handle newlines in author / committer

    rtomayko committed
    This shouldn't technically be allowed but we've seen a few cases of
    it in existing repositories on so let's just deal with
Commits on Jul 1, 2011
  1. @tmm1

    Merge pull request #78 from kevinsawicki/patch-1

    tmm1 committed
    Fix typo in tree method doc
  2. @kevinsawicki
Commits on Jun 22, 2011
  1. @rtomayko
  2. @rtomayko

    Grit::Git check_applies / patch related methods take command hash

    rtomayko committed
    This lets us pass an :env so we can use GIT_ALTERNATE_OBJECT_DIRECTORIES
    to check if a commit applies across repositories.
  3. @schacon @rtomayko

    tags api now resty

    schacon committed with rtomayko
  4. @schacon @rtomayko
  5. @schacon @rtomayko
Commits on Jun 15, 2011
  1. @rtomayko

    ruby rev_list passes --verify to native rev_parse in fallback

    rtomayko committed
    Otherwise, the git-rev-parse will return whatever is given as an arg
    when the ref doesn't exist. e.g.,
      $ git rev-parse some-bad-ref
      fatal: ambiguous argument 'some-bad-ref': unknown revision or path not in the working tree.
    The error message is on stderr and git-rev-parse exits with non-zero
    but the ref name is still output.
    The problem here is that code often calls rev_list like:
        git.rev_list({}, "some-bad-ref")
    Then rev_list tries to convert some-bad-ref to a SHA1, gets back the
    ref string, but continues on anyway. This eventually results in the
    rev_list failing to look up the object because it assumes its a SHA1
    when its really a ref string.
Commits on Jun 10, 2011
  1. @rtomayko

    Merge pull request #71 from injekt/master

    rtomayko committed
    Fix warnings on 1.9
  2. @rtomayko

    Merge pull request #72 from cesario/master

    rtomayko committed
    Fix the gemspec
  3. @franckverrot
Commits on Jun 9, 2011
  1. remove commented out lazy_reader

    Lee Jarvis committed
  2. fix warnings on Ruby 1.9

    Lee Jarvis committed
Commits on Jun 8, 2011
  1. @rtomayko
  2. @rtomayko
  3. @tmm1
  4. @tmm1

    Merge branch 'posix-spawn'

    tmm1 committed
  5. @tmm1
  6. @mojombo
  7. @schacon @rtomayko

    tree reading and writing

    schacon committed with rtomayko
  8. @schacon @rtomayko

    hm, guess we actually need this

    schacon committed with rtomayko
  9. @schacon @rtomayko
  10. @schacon @rtomayko
  11. @schacon @rtomayko

    tag creation and tests

    schacon committed with rtomayko
  12. @schacon @rtomayko

    updates to grit for tag api

    schacon committed with rtomayko
  13. @schacon @rtomayko

    commit listing and writing api

    schacon committed with rtomayko
  14. @schacon @rtomayko
Commits on Jun 1, 2011
  1. @mojombo

    Add Commit#patch_id.

    mojombo committed
Commits on May 30, 2011
  1. @rtomayko

    Merge pull request #60 from dkowis/fixing-spaces

    rtomayko committed
    Fix for files with leading or trailing spaces
  2. @rtomayko

    Merge pull request #68 from bobbyw/master

    rtomayko committed
    Default parameter for with_timeout incorrect
  3. @bobbywilson0
Commits on May 24, 2011
  1. @rtomayko
  2. @rtomayko

    handle packs disappearing between dir list and open

    rtomayko committed
    What happens is that we get a list of packfiles from but
    the files can disappear before the on the .idx or .pack
    file due to git-repack running at the same time. When this occurs,
    with_idx or with_pack would blow up with a NoMethodError because it
    tries to close the file in an ensure block, but the file was never
    This change causes the with_idx and with_pack methods to detect this
    situation and not yield to the block. This ought to result in
    correct behavior (the pack isn't really there) in most
Something went wrong with that request. Please try again.