Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jul 3, 2012
  1. @technoweenie
  2. @technoweenie
  3. @vmg @technoweenie

    strip newlines from tree entry names

    vmg authored technoweenie committed
    ported from github.com
  4. @technoweenie
  5. @technoweenie
Commits on Jun 29, 2012
  1. @jonmagic

    Remove un-needed hooks dir.

    jonmagic authored
  2. @jonmagic
  3. @jonmagic

    Added support for commit object with mergetag.

    jonmagic authored
    This actually just adds support for a tag in the commit that has single indented children. I'm totally making up what git_ruby.rev_list should return because I'm not sure how to build this actual test case as a dot_git fixture.
Commits on Apr 22, 2012
  1. @mojombo

    Release 2.5.0

    mojombo authored
  2. @mojombo

    Update History.

    mojombo authored
  3. @rtomayko @tmm1
  4. @rtomayko @tmm1

    Grit::Blame can load lines from cache

    rtomayko authored tmm1 committed
Commits on Jan 27, 2012
  1. @sr

    git ls-tree raises on non-zero exit

    sr authored
Commits on Dec 29, 2011
  1. @rtomayko

    Merge pull request #103 from peff/master

    rtomayko authored
    support large packfiles with index v2
Commits on Dec 23, 2011
  1. @peff

    support large packfiles with index v2

    peff authored
    Grit has known about the "v2" pack index format for a while.
    However, it never actually handled the extended offsets that
    we get when indexing packfiles that are larger than 2
    gigabytes.
    
    When an object is at an offset smaller than 2G, its byte
    offset into the packfile is placed in the first table of
    4-byte offset values. If it's past that, then the MSB is set
    on its offset in the 4-byte table, and the rest of the
    4-byte integer specifies an offset into an 8-byte table that
    follows.
    
    With this patch, grit should handle arbitrarily large packs
    (limited only by the pack format itself).
    
    A few notes on the patch itself:
    
      - I unpack using two "N" formats instead of "Q>", because
        "Q>" is not available in ruby < 1.9.3
    
      - No automated test is included, because you need a
        packfile that is greater than 2G. I did test it by hand.
Commits on Aug 20, 2011
  1. @vmg

    100% Git-compliant actor creation

    vmg authored
    Some more tweaks here:
    
    	- Do not use `strftime`, because it's not assured
    	to be cross-platform
    
    	- Use C-like string formatting for Great Glory
    	When Printing Numbers.
    
    	- Always print an email address -- even if we don't
    	have one. A missing email field will crash `fsck`.
Commits on Aug 17, 2011
  1. @vmg @defunkt

    Properly print time offsets

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

    handle newlines in author / committer

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

    Merge pull request #78 from kevinsawicki/patch-1

    tmm1 authored
    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 authored
    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 authored rtomayko committed
  4. @schacon @rtomayko
  5. @schacon @rtomayko

    we are not using these anymore. they are confusing

    schacon authored rtomayko committed
Commits on Jun 15, 2011
  1. @rtomayko

    ruby rev_list passes --verify to native rev_parse in fallback

    rtomayko authored
    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
      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 authored
    Fix warnings on 1.9
  2. @rtomayko

    Merge pull request #72 from cesario/master

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

    Lee Jarvis authored
  2. fix warnings on Ruby 1.9

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

    Merge branch 'posix-spawn'

    tmm1 authored
Something went wrong with that request. Please try again.