- 27 Oct, 2014 18 commits
-
-
`git_rebase_next` will apply the next patch (or cherry-pick) operation, leaving the results checked out in the index / working directory so that consumers can resolve any conflicts, as appropriate.
Edward Thomson committed -
Abort an in-progress rebase and move the working directory and repository back to the ORIG_HEAD state.
Edward Thomson committed -
Edward Thomson committed
-
Introduce `git_rebase` to set up a rebase session that can then be continued. Immediately, only merge-type rebase is supported.
Edward Thomson committed -
Clean up some warnings
Edward Thomson committed -
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Carlos Martín Nieto committed
-
Carlos Martín Nieto committed
-
- 26 Oct, 2014 1 commit
-
-
Linquize committed
-
- 24 Oct, 2014 11 commits
-
-
config: remove the refresh function and backend field
Edward Thomson committed -
remote: accept a repo and name for renaming
Edward Thomson committed -
Fixed memory leak in git_tag_delete()
Edward Thomson committed -
clar: use a custom temp directory name
Edward Thomson committed -
[RFC] Use CommonCrypto for hashing
Edward Thomson committed -
Pierre-Olivier Latour committed
-
Edward Thomson committed
-
remote: delete git_remote_supported_url()
Edward Thomson committed -
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 -
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 -
OSX has its own cryptographic library, let's make use of it instead of calling out to OpenSSL.
Carlos Martín Nieto committed
-
- 23 Oct, 2014 9 commits
-
-
We have been refreshing on read and write for a while now, so git_config_refresh() is at best a no-op, and might just end up wasting cycles.
Carlos Martín Nieto committed -
Refresh git configuration before looking for the tracking branch redux.
Carlos Martín Nieto committed -
ssl: dump the SSL ciphers in favour of TLS
Edward Thomson committed -
All versions of SSL are considered deprecated now, so let's ask OpenSSl to only use TLSv1. We still ask it to load those ciphers for compatibility with servers which want to use an older hello but will use TLS for encryption. For good measure we also disable compression, which can be exploitable, if the OpenSSL version supports it.
Carlos Martín Nieto committed -
Alan Rogers committed
-
Alan Rogers committed
-
Alan Rogers committed
-
describe: add example
Edward Thomson committed -
Remote paths: canonicalize UNC paths on Win32
Edward Thomson committed
-
- 22 Oct, 2014 1 commit
-
-
Git for Windows will handle UNC paths only when in forward-slash format, eg "//server/path". When given a UNC path as a remote, rewrite standard format ("\\server\path") into this ridiculous format.
Edward Thomson committed
-