- 17 Mar, 2015 1 commit
-
-
Otherwise, bailing out early when ls_to_vector() fails accesses uninitialized memory.
Sebastian Bauer committed
-
- 11 Mar, 2015 1 commit
-
-
Pierre-Olivier Latour committed
-
- 03 Mar, 2015 3 commits
-
-
This changes the get_entry() method to return a refcounted version of the config entry, which you have to free when you're done. This allows us to avoid freeing the memory in which the entry is stored on a refresh, which may happen at any time for a live config. For this reason, get_string() has been forbidden on live configs and a new function get_string_buf() has been added, which stores the string in a git_buf which the user then owns. The functions which parse the string value takea advantage of the borrowing to parse safely and then release the entry.
Carlos Martín Nieto committed -
We always use "update by push".
Carlos Martín Nieto committed -
The signature for the reflog is not something which changes dynamically. Almost all uses will be NULL, since we want for the repository's default identity to be used, making it noise. In order to allow for changing the identity, we instead provide git_repository_set_ident() and git_repository_ident() which allow a user to override the choice of signature.
Carlos Martín Nieto committed
-
- 13 Feb, 2015 1 commit
-
-
Introduce some helper macros to test integer overflow from arithmetic and set error message appropriately.
Edward Thomson committed
-
- 08 Jan, 2015 1 commit
-
-
Edward Thomson committed
-
- 05 Jan, 2015 2 commits
-
-
David Calavera committed
-
David Calavera committed
-
- 01 Jan, 2015 1 commit
-
-
git_remote_download() must also clear the internal push state resulting from a possible earlier push operation. Otherwise calling git_remote_update_tips() will execute the push version instead of the fetch version and among other things, tags won't be updated.
Pierre-Olivier Latour committed
-
- 30 Dec, 2014 1 commit
-
-
Instead we provide git_remote_upload() and git_remote_update_tips() in order to have a parallel API for fetching and pushing.
Carlos Martín Nieto committed
-
- 14 Dec, 2014 5 commits
-
-
This option does not get persisted to disk, which makes it different from the rest of the setters. Remove it until we go all the way. We still respect the configuration option, and it's still possible to perform a one-time prune by calling the function.
Carlos Martín Nieto committed -
For each remote-tracking branch we want to remove, we need to consider it against every other refspec in case we have overlapping refspecs, such as with refs/heads/*:refs/remotes/origin/* refs/pull/*/head:refs/remotes/origin/pr/* as we'd otherwise remove too many refspecs. Create a list of condidates, which are the references matching the rhs of any active refspec and then filter that list by removing those entries for which we find a remove reference with any active refspec. Those which are left after this are removed.
Carlos Martín Nieto committed -
This makes a fetch+prune more similar to a connect+prune and makes it more likely that we see errors in the decision to prune a reference.
Carlos Martín Nieto committed -
David Calavera committed
-
Linquize committed
-
- 10 Dec, 2014 1 commit
-
-
The push cannot be successful if we sent a bad packfile. We should return an error in that case instead of storing it elsewhere.
Carlos Martín Nieto committed
-
- 23 Nov, 2014 2 commits
-
-
Carlos Martín Nieto committed
-
Valgrind is now clean except for libssl and libgcrypt.
Carlos Martín Nieto committed
-
- 19 Nov, 2014 1 commit
-
-
Make it clear that this is not the ls-remote command but a way to access the data we have and how long it's kept around.
Carlos Martín Nieto committed
-
- 17 Nov, 2014 1 commit
-
-
When creating a new remote, contrary to loading one from disk, active_refspecs was not populated. This means that if using the new remote to push, git_push_update_tips() will be a no-op since it checks the refspecs passed during the push against the base ones i.e. active_refspecs. And therefore the local refs won't be created or updated after the push operation.
Pierre-Olivier Latour committed
-
- 08 Nov, 2014 7 commits
-
-
If the user does not pass any refspecs to push, try to use those configured via the configuration or via add_push().
Carlos Martín Nieto committed -
This function, similar in style to git_remote_fetch(), performs all the steps required for a push, with a similar interface. The remote callbacks struct has learnt about the push callbacks, letting us set the callbacks a single time instead of setting some in the remote and some in the push operation.
Carlos Martín Nieto committed -
Pierre-Olivier Latour committed
-
This is an ugly chunk of code, so let's put it into its own function.
Carlos Martín Nieto committed -
If the remote is anonymous, then we cannot check for any configuration, as there is no name. Check for this before we try to use the name, which may be a NULL pointer. This fixes #2697.
Carlos Martín Nieto committed -
This reduces the clutter somewhat and lets us see what we're asking about the reference.
Carlos Martín Nieto committed -
This brings it in line with the rest of the lookup functions.
Carlos Martín Nieto committed
-
- 03 Nov, 2014 2 commits
-
-
Edward Thomson committed
-
Before trying to rtransform using the given refspec to figure out what the name of the upstream branch is on the remote, we must make sure that the target of the refspec applies to the current branch's upstream.
Carlos Martín Nieto committed
-
- 02 Nov, 2014 1 commit
-
-
The create function with default refspec is the same as the one with a custom refspec, but it has the default refspec, so we can create the one on top of the other.
Carlos Martín Nieto committed
-
- 27 Oct, 2014 3 commits
-
-
Pierre-Olivier Latour committed
-
Edward Thomson committed
-
Edward Thomson committed
-
- 24 Oct, 2014 1 commit
-
-
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
-
- 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
-
- 10 Oct, 2014 1 commit
-
-
Arthur Schreiber committed
-
- 09 Oct, 2014 1 commit
-
-
Carlos Martín Nieto committed
-
- 30 Sep, 2014 2 commits
-
-
We don't need the remote loaded, and the function extracted both of these from the git_remote in order to do its work, so let's remote a step and not ask for the loaded remote at all. This fixes #2390.
Carlos Martín Nieto committed -
When a list of refspecs is passed to fetch (what git would consider refspec passed on the command-line), we not only need to perform the updates described in that refspec, but also update the remote-tracking branch of the fetched remote heads according to the remote's configured refspecs. These "fetches" are not however to be written to FETCH_HEAD as they would be duplicate data, and it's not what the user asked for.
Carlos Martín Nieto committed
-