- Nov 03, 2014
-
-
Jacques Germishuys authored
-
Carlos Martín Nieto authored
An anonymous remote wouldn't create remote-tracking branches, so testing we don't create them for TAGS_ALL is nonsensical. Furthermore, the name of the supposed remote-tracking branch was also not one which would have been created had it had a name. Give the remote a name and test that we only create the tags when we pass TAGS_ALL and that we do create the remote-branch branch when given TAGS_AUTO.
-
Carlos Martín Nieto authored
Since it's not necessarily obvious, mention the merging state and how to clear it.
-
- Oct 28, 2014
-
-
Edward Thomson authored
revert tests: always use core.autocrlf=false in tests
-
Edward Thomson authored
-
Edward Thomson authored
Fixed the most obvious Clang static analyzer warnings
-
Pierre-Olivier Latour authored
-
Pierre-Olivier Latour authored
-
- Oct 27, 2014
-
-
Edward Thomson authored
Flip THREADSAFE's default to ON
-
Carlos Martín Nieto authored
-
Carlos Martín Nieto authored
Threads are here to stay; and for a while now, users have had to call the initialization function which sets up threads and crypto regardless of whether the library was built threadsafe or not.
-
Edward Thomson authored
-
Sven Strickroth authored
Signed-off-by:
Sven Strickroth <email@cs-ware.de>
-
Edward Thomson authored
Rebase (merge)
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
Rename git_merge_head to git_annotated_commit, as it becomes used in more operations than just merge.
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
Already cherry-picked commits should not be re-included. If all changes included in a commit exist in the upstream, then we should error with GIT_EAPPLIED.
-
Edward Thomson authored
Commit the current patch of a rebase process.
-
Edward Thomson authored
-
Edward Thomson authored
`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 authored
Abort an in-progress rebase and move the working directory and repository back to the ORIG_HEAD state.
-
Edward Thomson authored
-
Edward Thomson authored
Introduce `git_rebase` to set up a rebase session that can then be continued. Immediately, only merge-type rebase is supported.
-
Edward Thomson authored
Clean up some warnings
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-
Edward Thomson authored
-