- 02 Oct, 2013 9 commits
-
-
The removal of many options which lead to the direct usage of the user's checkout options means we should make sure they remain const.
Carlos Martín Nieto committed -
This used to be done via transport flags, which was removed in a previous commit.
Carlos Martín Nieto committed -
The basic clone function is there to make it easy to create a "normal" clone. Remove a bunch of options that are about changing the remote's configuration.
Carlos Martín Nieto committed -
Unify the code bases.
Carlos Martín Nieto committed -
Downloading all tags is part of what makes it a clone instead of simply a fetch.
Carlos Martín Nieto committed -
Carlos Martín Nieto committed
-
This allows you to set up the repository and remote as you which to have them before performing the clone operation.
Carlos Martín Nieto committed -
Move this one as well, letting us have a single way of setting the callbacks for the remote, and removing fields from the clone options.
Carlos Martín Nieto committed -
The text progress and update_tips callbacks are already part of the struct, which was meant to unify the callback setup, but the download one was left out.
Carlos Martín Nieto committed
-
- 01 Oct, 2013 7 commits
-
-
Add git_transport_register, git_transport_unregister
Vicent Martí committed -
Philip Kelley committed
-
Ben Straub committed
-
Config subsection name should allow to have ']' and '\\' should allow to escape any characters
Vicent Martí committed -
Linquize committed
-
Linquize committed
-
Linquize committed
-
- 30 Sep, 2013 9 commits
-
-
Redir refactor
Vicent Martí committed -
Initial Implementation of progress reports during push
Vicent Martí committed -
Never consider submodules for stashing
Vicent Martí committed -
...before the helper's cleanup method tries to delete their files.
Ben Straub committed -
Fix x86/x64 size_t related warnings
Vicent Martí committed -
This adds the basics of progress reporting during push. While progress for all aspects of a push operation are not reported with this change, it lays the foundation to add these later. Push progress reporting can be improved in the future - and consumers of the API should just get more accurate information at that point. The main areas where this is lacking are: 1) packbuilding progress: does not report progress during deltafication, as this involves coordinating progress from multiple threads. 2) network progress: reports progress as objects and bytes are going to be written to the subtransport (instead of as client gets confirmation that they have been received by the server) and leaves out some of the bytes that are transfered as part of the push protocol. Basically, this reports the pack bytes that are written to the subtransport. It does not report the bytes sent on the wire that are received by the server. This should be a good estimate of progress (and an improvement over no progress).
Jameson Miller committed -
Remove leading newlines from commit message
Vicent Martí committed -
Fix libgit2/libgit2sharp#522
nulltoken committed -
nulltoken committed
-
- 28 Sep, 2013 2 commits
-
-
Justin Spahr-Summers committed
-
Justin Spahr-Summers committed
-
- 27 Sep, 2013 2 commits
-
-
Add refdb.h to git2.h, reorder git2.h sanely
Vicent Martí committed -
Edward Thomson committed
-
- 26 Sep, 2013 9 commits
-
-
Ben Straub committed
-
Ben Straub committed
-
Ben Straub committed
-
Ben Straub committed
-
...and have that call manage replaced memory in the output structure.
Ben Straub committed -
Ben Straub committed
-
nulltoken committed
-
Ben Straub committed
-
Ben Straub committed
-
- 25 Sep, 2013 2 commits
-
-
Ben Straub committed
-
Win32: handle http->https redirects
Ben Straub committed
-