1. 08 Nov, 2014 3 commits
  2. 07 Nov, 2014 1 commit
  3. 27 Oct, 2014 3 commits
  4. 24 Oct, 2014 2 commits
    • remote: accept a repo and name for renaming · 46c8f7f8
      Remote objects are not meant to be changed from under the user. We did
      this in rename, but only the name and left the refspecs, such that a
      save would save the wrong refspecs (and a fetch and anything else would
      use the wrong refspecs).
      
      Instead, let's simply take a name and not change any loaded remote from
      under the user.
      Carlos Martín Nieto committed
    • remote: delete git_remote_supported_url() · 0862f617
      This function does not in fact tell us anything, as almost anything with
      a colon in it is a valid rsync-style SSH path; it can not tell us that
      we do not support ftp or afp or similar as those are still valid SSH
      paths and we do support that.
      Carlos Martín Nieto committed
  5. 10 Oct, 2014 1 commit
  6. 09 Oct, 2014 1 commit
  7. 05 Oct, 2014 1 commit
  8. 30 Sep, 2014 3 commits
  9. 24 Sep, 2014 1 commit
  10. 27 Aug, 2014 1 commit
  11. 14 Aug, 2014 1 commit
    • Custom transport: minor cleanups · c180c065
       * Move the transport registration mechanisms into a new header under
         'sys/' because this is advanced stuff.
       * Remove the 'priority' argument from the registration as it adds
         unnecessary complexity.  (Since transports cannot decline to operate,
         only the highest priority transport is ever executed.)  Users who
         require per-priority transports can implement that in their custom
         transport themselves.
       * Simplify registration further by taking a scheme (eg "http") instead
         of a prefix (eg "http://").
      Edward Thomson committed
  12. 27 Jul, 2014 1 commit
  13. 07 Jul, 2014 1 commit
  14. 04 Jul, 2014 1 commit
  15. 02 Jul, 2014 2 commits
  16. 27 Jun, 2014 1 commit
  17. 24 Jun, 2014 4 commits
  18. 23 Jun, 2014 1 commit