1. 14 May, 2015 1 commit
  2. 13 May, 2015 4 commits
  3. 17 Mar, 2015 1 commit
  4. 11 Mar, 2015 2 commits
    • local: create pack with multiple threads · 0ef54a63
      The default behaviour for the packbuilder is to perform the work in a
      single thread, which is fine for the public API, but we currently have
      no way for a user to determine the number of threads to use when
      creating the packfile, which makes our clone behaviour over the
      filesystem quite a bit slower than what git offers.
      
      This is a very particular scenario, in which we avoid spawning git by
      being ourselves the server-side, so it's probably ok to auto-set the
      threading, as the upload-pack process would do if we were talking to
      git.
      Carlos Martín Nieto committed
    • local: let the packbuilder perform smarter object insertion · e68b31a1
      Currently we use the most naïve and inefficient method for figuring out
      which objects to send to the remote whereby we end up trying to insert
      subdirs which have not changed multiple times.
      
      Instead, make use of the packbuilder's built-in more efficient method
      which uses the walk to feed the object list and avoids inserting an
      object and its descendants.
      Carlos Martín Nieto committed
  5. 03 Mar, 2015 1 commit
    • Remove the signature from ref-modifying functions · 659cf202
      The signature for the reflog is not something which changes
      dynamically. Almost all uses will be NULL, since we want for the
      repository's default identity to be used, making it noise.
      
      In order to allow for changing the identity, we instead provide
      git_repository_set_ident() and git_repository_ident() which allow a user
      to override the choice of signature.
      Carlos Martín Nieto committed
  6. 13 Feb, 2015 1 commit
  7. 29 Dec, 2014 1 commit
  8. 16 Dec, 2014 1 commit
  9. 23 Nov, 2014 2 commits
  10. 09 Nov, 2014 1 commit
    • push: use the common refspec parser · aad638f3
      There is one well-known and well-tested parser which we should use,
      instead of implementing parsing a second time.
      
      The common parser is also augmented to copy the LHS into the RHS if the
      latter is empty.
      
      The expressions test had to change a bit, as we now catch a bad RHS of a
      refspec locally.
      Carlos Martín Nieto committed
  11. 03 Jun, 2014 1 commit
  12. 22 May, 2014 1 commit
  13. 21 May, 2014 1 commit
  14. 21 Apr, 2014 1 commit
  15. 07 Mar, 2014 1 commit
  16. 19 Jan, 2014 1 commit
  17. 17 Jan, 2014 1 commit
  18. 15 Jan, 2014 1 commit
  19. 11 Dec, 2013 2 commits
    • Remove converting user error to GIT_EUSER · 25e0b157
      This changes the behavior of callbacks so that the callback error
      code is not converted into GIT_EUSER and instead we propagate the
      return value through to the caller.  Instead of using the
      giterr_capture and giterr_restore functions, we now rely on all
      functions to pass back the return value from a callback.
      
      To avoid having a return value with no error message, the user
      can call the public giterr_set_str or some such function to set
      an error message.  There is a new helper 'giterr_set_callback'
      that functions can invoke after making a callback which ensures
      that some error message was set in case the callback did not set
      one.
      
      In places where the sign of the callback return value is
      meaningful (e.g. positive to skip, negative to abort), only the
      negative values are returned back to the caller, obviously, since
      the other values allow for continuing the loop.
      
      The hardest parts of this were in the checkout code where positive
      return values were overloaded as meaningful values for checkout.
      I fixed this by adding an output parameter to many of the internal
      checkout functions and removing the overload.  This added some
      code, but it is probably a better implementation.
      
      There is some funkiness in the network code where user provided
      callbacks could be returning a positive or a negative value and
      we want to rely on that to cancel the loop.  There are still a
      couple places where an user error might get turned into GIT_EUSER
      there, I think, though none exercised by the tests.
      Russell Belfer committed
    • Add config read fns with controlled error behavior · 9f77b3f6
      This adds `git_config__lookup_entry` which will look up a key in
      a config and return either the entry or NULL if the key was not
      present.  Optionally, it can either suppress all errors or can
      return them (although not finding the key is not an error for this
      function).  Unlike other accessors, this does not normalize the
      config key string, so it must only be used when the key is known
      to be in normalized form (i.e. all lower-case before the first dot
      and after the last dot, with no invalid characters).
      
      This also adds three high-level helper functions to look up config
      values with no errors and a fallback value.  The three functions
      are for string, bool, and int values, and will resort to the
      fallback value for any error that arises.  They are:
      
      * `git_config__get_string_force`
      * `git_config__get_bool_force`
      * `git_config__get_int_force`
      
      None of them normalize the config `key` either, so they can only
      be used for internal cases where the key is known to be in normal
      format.
      Russell Belfer committed
  20. 11 Nov, 2013 1 commit
    • remote: make _ls return the list directly · 359dce72
      The callback-based method of listing remote references dates back to the
      beginning of the network code's lifetime, when we didn't know any
      better.
      
      We need to keep the list around for update_tips() after disconnect() so
      let's make use of this to simply give the user a pointer to the array so
      they can write straightforward code instead of having to go through a
      callback.
      Carlos Martín Nieto committed
  21. 30 Oct, 2013 1 commit
    • indexer: remove the stream infix · a6154f21
      It was there to keep it apart from the one which read in from a file on
      disk. This other indexer does not exist anymore, so there is no need for
      anything other than git_indexer to refer to it.
      
      While here, rename _add() function to _append() and _finalize() to
      _commit(). The former change is cosmetic, while the latter avoids
      talking about "finalizing", which OO languages use to mean something
      completely different.
      Carlos Martín Nieto committed
  22. 02 Oct, 2013 1 commit
  23. 04 Sep, 2013 1 commit
  24. 15 Aug, 2013 1 commit
  25. 25 Jun, 2013 2 commits
  26. 24 Jun, 2013 1 commit
  27. 15 May, 2013 2 commits
  28. 11 May, 2013 1 commit
    • refs: remove the OID/SYMBOLIC filtering · 2b562c3a
      Nobody should ever be using anything other than ALL at this level, so
      remove the option altogether.
      
      As part of this, git_reference_foreach_glob is now implemented in the
      frontend using an iterator. Backends will later regain the ability of
      doing the glob filtering in the backend.
      Carlos Martín Nieto committed
  29. 29 Apr, 2013 1 commit
  30. 15 Apr, 2013 2 commits
  31. 09 Apr, 2013 1 commit