1. 26 Jun, 2015 1 commit
  2. 22 May, 2015 1 commit
    • branch: error out if we cannot find the remote · 5014fe95
      When we look for which remote corresponds to a remote-tracking branch,
      we look in the refspecs to see which ones matches. If none do, we should
      abort. We currently ignore the error message from this operation, so
      let's not do that anymore.
      
      As part of the test we're writing, let's test for the expected behaviour
      if we cannot find a refspec which tells us what the remote-tracking
      branch for a remote would look like.
      Carlos Martín Nieto committed
  3. 13 May, 2015 1 commit
    • remote: remove live changing of refspecs · 77254990
      The base refspecs changing can be a cause of confusion as to what is the
      current base refspec set and complicate saving the remote's
      configuration.
      
      Change `git_remote_add_{fetch,push}()` to update the configuration
      instead of an instance.
      
      This finally makes `git_remote_save()` a no-op, it will be removed in a
      later commit.
      Carlos Martín Nieto committed
  4. 16 Mar, 2015 1 commit
  5. 08 Mar, 2015 1 commit
  6. 04 Mar, 2015 2 commits
  7. 03 Mar, 2015 4 commits
  8. 03 Feb, 2015 2 commits
  9. 16 Dec, 2014 1 commit
  10. 22 Nov, 2014 1 commit
    • peel: reject bad queries with EINVALIDSPEC · 753e17b0
      There are some combination of objects and target types which we know
      cannot be fulfilled. Return EINVALIDSPEC for those to signify that there
      is a mismatch in the user-provided data and what the object model is
      capable of satisfying.
      
      If we start at a tag and in the course of peeling find out that we
      cannot reach a particular type, we return EPEEL.
      Carlos Martín Nieto committed
  11. 17 Nov, 2014 1 commit
  12. 08 Nov, 2014 1 commit
  13. 09 Oct, 2014 1 commit
  14. 30 Sep, 2014 1 commit
    • Introduce reference transactions · ab8d9242
      A transaction allows you to lock multiple references and set up changes
      for them before applying the changes all at once (or as close as the
      backend supports).
      
      This can be used for replication purposes, or for making sure some
      operations run when the reference is locked and thus cannot be changed.
      Carlos Martín Nieto committed
  15. 05 Aug, 2014 1 commit
  16. 01 Jul, 2014 1 commit
  17. 02 Jun, 2014 1 commit
  18. 30 May, 2014 2 commits
  19. 08 May, 2014 2 commits
    • Don't always test composed-insensitive lookups · 8a2ef218
      Only on a filesystem that is composed/decomposed insensitive,
      should be testing that a branch can be looked up by the opposite
      form and still work correctly.
      Russell Belfer committed
    • Pass unconverted data when iconv doesn't like it · 43a04135
      When using Iconv to convert unicode data and iconv doesn't like
      the source data (because it thinks that it's not actual UTF-8),
      instead of stopping the operation, just use the unconverted data.
      This will generally do the right thing on the filesystem, since
      that is the source of the non-UTF-8 path data anyhow.
      
      This adds some tests for creating and looking up branches with
      messy Unicode names.  Also, this takes the helper function that
      was previously internal to `git_repository_init` and makes it
      into `git_path_does_fs_decompose_unicode` which is a useful in
      tests to understand what the expected results should be.
      Russell Belfer committed
  20. 02 May, 2014 1 commit
  21. 16 Apr, 2014 1 commit
  22. 20 Mar, 2014 1 commit
  23. 19 Mar, 2014 1 commit
  24. 17 Mar, 2014 1 commit
  25. 02 Mar, 2014 1 commit
  26. 10 Feb, 2014 1 commit
  27. 05 Feb, 2014 6 commits
  28. 03 Feb, 2014 1 commit