- 02 Apr, 2014 2 commits
-
-
Cloning from an empty repo must set master's upstream to origin's master, even if neither of them exist. Fetching from a non-empty origin must then mark the master branch for-merge. This currently fails.
Carlos Martín Nieto committed -
Russell Belfer committed
-
- 01 Apr, 2014 1 commit
-
-
The order in this function is the opposite to what create_with_fetchspec() has, so change this one, as url-then-refspec is what git does. As we need to break compilation and the swap doesn't do that, let's take this opportunity to rename in-memory remotes to anonymous as that's really what sets them apart.
Carlos Martín Nieto committed
-
- 31 Mar, 2014 3 commits
-
-
Anurag Gupta committed
-
Russell Belfer committed
-
Edward Thomson committed
-
- 29 Mar, 2014 1 commit
-
-
Edward Thomson committed
-
- 28 Mar, 2014 2 commits
-
-
Edward Thomson committed
-
Edward Thomson committed
-
- 27 Mar, 2014 1 commit
-
-
Russell Belfer committed
-
- 26 Mar, 2014 4 commits
-
-
When a submodule was inserted with a different path and name, the return value from khash greater than zero was allowed to propagate back out to the caller when it should really be zeroed. This led to a possible crash when reloading submodules if that was the first time that submodule data was loaded.
Russell Belfer committed -
The reload_all call could end up dereferencing a NULL pointer if there was an error while attempting to load the submodules config data (i.e. invalid content in the gitmodules file). This fixes it.
Russell Belfer committed -
Edward Thomson committed
-
Edward Thomson committed
-
- 25 Mar, 2014 2 commits
-
-
When a directory containing a .git directory (or even just a plain gitlink) was found, libgit2 was going out of its way to treat it specially. This seemed like it was necessary because the diff code was not originally emulating Git's behavior for untracked directories correctly (i.e. scanning for ignored vs untracked items inside). Now that libgit2 diff mimics Git's untracked directory behavior, the special handling for contained Git repos is actually incorrect and this commit rips it out.
Russell Belfer committed -
`git_submodule` objects were already refcounted internally in case the submodule name was different from the path at which it was stored. This makes that refcounting externally used as well, so `git_submodule_lookup` and `git_submodule_add_setup` return an object that requires a `git_submodule_free` when done.
Russell Belfer committed
-
- 24 Mar, 2014 5 commits
-
-
Anurag Gupta committed
-
Anurag Gupta committed
-
Anurag Gupta committed
-
Edward Thomson committed
-
This survived the last round of culling, as the signature is only in the comments.
Carlos Martín Nieto committed
-
- 20 Mar, 2014 10 commits
-
-
On bare by default, or when core.logallrefupdates is false, we must not write the reflog.
Carlos Martín Nieto 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
-
- 19 Mar, 2014 3 commits
-
-
Given HEAD -> master -> foo, when updating foo's reflog we should also update HEAD's, as it's considered the current branch.
Carlos Martín Nieto committed -
The reflog append function was overzealous in its checking. When passed an old and new ids, it should not do any checking, but just serialize the data to a reflog entry.
Carlos Martín Nieto committed -
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
-
- 18 Mar, 2014 2 commits
-
-
The existing ones lack checking zeroed ids when switching back from an unborn branch as well as what happens when detaching. The reflog appending function mistakenly wrote zeros when dealing with a detached HEAD. This explicitly checks for those situations and fixes them.
Carlos Martín Nieto committed -
Aimeast committed
-
- 17 Mar, 2014 2 commits
-
-
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 -
This is not something anybody would ever do; removing HEAD makes the .git/ directory no longer be a repository, so we wouldn't be expected to handle such a situation.
Carlos Martín Nieto committed
-
- 12 Mar, 2014 1 commit
-
-
If the pqueue comparison fn returned just 0 or 1 (think "a<b") then the sort order of returned items could be wrong because there was a "< 0" that really needed to be "<= 0". Yikes!!!
Russell Belfer committed
-
- 10 Mar, 2014 1 commit
-
-
Jiri Pospisil committed
-