Skip to content
Commits on Jun 24, 2010
  1. only way this would work

    committed
Commits on Apr 10, 2010
Commits on Jan 21, 2010
  1. @geoffgarside

    Update Website

    geoffgarside committed
  2. @geoffgarside

    Enable RUN_CLANG_STATIC_ANALYZER when building Git framework target o…

    geoffgarside committed
    …r else I'll never remember to run it. #csa
  3. @geoffgarside
  4. @geoffgarside
  5. @geoffgarside
  6. @geoffgarside

    Ensure tzStr is released after creating GITDateTime object from bytes…

    geoffgarside committed
    … in GITTag and GITCommit. #csa
  7. @geoffgarside
  8. @geoffgarside

    Rename {create => new}StringWithObjectRecord methods to better comply…

    geoffgarside committed
    … with apple guidelines on method naming to indicate object ownership
Commits on Jan 20, 2010
  1. @geoffgarside
Commits on Jan 19, 2010
  1. @geoffgarside
Commits on Jan 18, 2010
  1. @geoffgarside
  2. @geoffgarside
  3. @geoffgarside
  4. @geoffgarside
  5. @geoffgarside
Commits on Jan 17, 2010
  1. @geoffgarside
  2. @geoffgarside

    Rename GITRepo -remotes to GITRepo -remoteBranches and return an arra…

    geoffgarside committed
    …y of GITBranch objects instead of GITRefs
  3. @geoffgarside
  4. @geoffgarside
  5. @geoffgarside
  6. @geoffgarside
  7. @geoffgarside
  8. @geoffgarside

    Update Website

    geoffgarside committed
  9. @geoffgarside
  10. @geoffgarside

    Massive bug fix.

    geoffgarside committed
    GITObject subclasses were detecting their SHA1 hash values by hashing their data contents when being created. This is wrong as the sha1 values are calculated from the "$type $size" prefixed objects as they are written to the file system. The SHA1 hash values are now passed directly into the objects as they are created. This alteration required modification to all classes which load objects from either the file system or PACK files.
  11. @geoffgarside
  12. @geoffgarside
  13. @geoffgarside
  14. @geoffgarside
  15. @geoffgarside

    Fix some GITRepo comments

    geoffgarside committed
  16. @geoffgarside
  17. @geoffgarside
  18. @geoffgarside
Something went wrong with that request. Please try again.