- 26 Jun, 2015 1 commit
-
-
Vicent Marti committed
-
- 22 May, 2015 1 commit
-
-
When we look for which remote corresponds to a remote-tracking branch, we look in the refspecs to see which ones matches. If none do, we should abort. We currently ignore the error message from this operation, so let's not do that anymore. As part of the test we're writing, let's test for the expected behaviour if we cannot find a refspec which tells us what the remote-tracking branch for a remote would look like.
Carlos Martín Nieto committed
-
- 13 May, 2015 1 commit
-
-
The base refspecs changing can be a cause of confusion as to what is the current base refspec set and complicate saving the remote's configuration. Change `git_remote_add_{fetch,push}()` to update the configuration instead of an instance. This finally makes `git_remote_save()` a no-op, it will be removed in a later commit.
Carlos Martín Nieto committed
-
- 16 Mar, 2015 1 commit
-
-
This also brings the soft-reset tests back to life. The function name was missing an underscore, meaning they had not been running.
Carlos Martín Nieto committed
-
- 08 Mar, 2015 1 commit
-
-
When we rename a reference, we want the old and new ids to be the same one (as we did not change it). The normal code path looks up the old id from the current value of the brtanch, but by the time we look it up, it does not exist anymore and thus we write a zero id. Pass the old id explicitly instead.
Carlos Martín Nieto committed
-
- 04 Mar, 2015 2 commits
- 03 Mar, 2015 4 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 want to use the "checkout: moving from ..." message in order to let git know when a change of branch has happened. Make the convenience functions for this goal write this message.
Carlos Martín Nieto committed -
This namespace is about behaving like git's branch command, so let's do exactly that instead of taking a reflog message. This override is still available via the reference namespace.
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
-
- 03 Feb, 2015 2 commits
-
-
Jeff Hostetler committed
-
Edward Thomson committed
-
- 16 Dec, 2014 1 commit
-
-
Validate loose reference names on Win32.
Edward Thomson committed
-
- 22 Nov, 2014 1 commit
-
-
There are some combination of objects and target types which we know cannot be fulfilled. Return EINVALIDSPEC for those to signify that there is a mismatch in the user-provided data and what the object model is capable of satisfying. If we start at a tag and in the course of peeling find out that we cannot reach a particular type, we return EPEEL.
Carlos Martín Nieto committed
-
- 17 Nov, 2014 1 commit
-
-
Carlos Martín Nieto committed
-
- 08 Nov, 2014 1 commit
-
-
This gets the value from branch.<foo>.remote.
Carlos Martín Nieto committed
-
- 09 Oct, 2014 1 commit
-
-
This leaves space for future expansion to locking other resources without having to change the API for references.
Carlos Martín Nieto committed
-
- 30 Sep, 2014 1 commit
-
-
A transaction allows you to lock multiple references and set up changes for them before applying the changes all at once (or as close as the backend supports). This can be used for replication purposes, or for making sure some operations run when the reference is locked and thus cannot be changed.
Carlos Martín Nieto committed
-
- 05 Aug, 2014 1 commit
-
-
Jacques Germishuys committed
-
- 01 Jul, 2014 1 commit
-
-
Edward Thomson committed
-
- 02 Jun, 2014 1 commit
-
-
If we remove a reference while we're iterating through the packed refs, the position in the iterator will be off.
Carlos Martín Nieto committed
-
- 30 May, 2014 2 commits
-
-
This adds another assertion to ensure that the reference name inside the git_reference struct returned by `git_branch_create` is returned as precomposed if `core.precomposeunicode` is enabled.
Arthur Schreiber committed -
This tests that decomposed branch names are correctly precomposed when passed to `git_branch_move` and `core.precomposeunicode` is enabled.
Arthur Schreiber committed
-
- 08 May, 2014 2 commits
-
-
Only on a filesystem that is composed/decomposed insensitive, should be testing that a branch can be looked up by the opposite form and still work correctly.
Russell Belfer committed -
When using Iconv to convert unicode data and iconv doesn't like the source data (because it thinks that it's not actual UTF-8), instead of stopping the operation, just use the unconverted data. This will generally do the right thing on the filesystem, since that is the source of the non-UTF-8 path data anyhow. This adds some tests for creating and looking up branches with messy Unicode names. Also, this takes the helper function that was previously internal to `git_repository_init` and makes it into `git_path_does_fs_decompose_unicode` which is a useful in tests to understand what the expected results should be.
Russell Belfer committed
-
- 02 May, 2014 1 commit
-
-
Trying to find other issues where tests may not clean up quite properly when they are through...
Russell Belfer committed
-
- 16 Apr, 2014 1 commit
-
-
git_branch_t is an enum so requesting GIT_BRANCH_LOCAL | GIT_BRANCH_REMOTE is not possible as it is not a member of the enum (at least VS2013 C++ complains about it). This fixes a regression introduced in commit a667ca82 (PR #1946). Signed-off-by: Sven Strickroth <email@cs-ware.de>
Sven Strickroth committed
-
- 20 Mar, 2014 1 commit
-
-
On bare by default, or when core.logallrefupdates is false, we must not write the reflog.
Carlos Martín Nieto committed
-
- 19 Mar, 2014 1 commit
-
-
If the caller wants to update a ref to point to the same target as it currently has, we should return early and avoid writing to the reflog.
Carlos Martín Nieto committed
-
- 17 Mar, 2014 1 commit
-
-
When we update the current branch, we must also append to HEAD's reflog to keep them in sync. This is a bit of a hack, but as git.git says, it covers 100% of default cases.
Carlos Martín Nieto committed
-
- 02 Mar, 2014 1 commit
-
-
Linquize committed
-
- 10 Feb, 2014 1 commit
-
-
Keep the reflog parameters as the last two, as they're the optional parameters.
Carlos Martín Nieto committed
-
- 05 Feb, 2014 6 commits
-
-
Add it under the git_reference_remove() name, letting the user pass the repo and name, analogous to unconditional setting/creation.
Carlos Martín Nieto committed -
If the type of the on-disk reference has changed, the old value comparison should fail.
Carlos Martín Nieto committed -
Recognize when the reference has changed since we loaded it.
Carlos Martín Nieto committed -
Bring the race detection goodness to symbolic references as well.
Carlos Martín Nieto committed -
Carlos Martín Nieto committed
-
Ben Straub committed
-
- 03 Feb, 2014 1 commit
-
-
Ben Straub committed
-