| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
git_branch_t.
|
| |
|
|
|
|
|
|
| |
Create a git_branch_iterator type which is equivalent to the foreach but
lets us write loops instead of callbacks.
Since the introduction of git_reference_shorthand(), the added value of
passing the name is reduced.
|
| |\
| |
| | |
Make reflog part of refdb
|
| | |
| |
| |
| |
| | |
Provide a function that reads a reflog, performs an append and writes back to the
backend in one call.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
References and their logs are logically coupled, let's make it so in
the code by moving the fs-based reflog implementation to live next to
the fs-based refs one.
As part of the change, make the function take names rather than
references, as only the names are relevant when looking up and
handling reflogs.
|
| |\ \
| | |
| | | |
Provide the user with a more useful error code when a looking up a reference which name points to a namepace
|
| | | |
| | |
| | |
| | |
| | | |
This lets the reference code return not-found when the user asks to
look up a reference when in fact they pass a namespace.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Before these changes, looking up a reference would return the
same precomposed or decomposed form of the reference name that
was used to look it up, so on MacOS which ignores the difference
between the two, a single reference could be looked up either way
and git_reference_name would return the form of the name that was
used to look it up! This change makes lookup always return the
precomposed name if core.precomposeunicode is set regardless of
which version was used to look it up. The reference iterator was
already returning the precomposed form from earlier work.
This also updates the CMakeLists.txt rules for enabling iconv
usage because the clar tests for this code were actually not being
activated properly with the old version.
Finally, this moves git_repository_reset_filesystem from include/
git2/repository.h to include/git2/sys/repository.h since it is not
really a function that normal library users should have to think
about very often.
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This cleans up some additional issues. The main change is that
on a filesystem that doesn't support mode bits, libgit2 will now
create new blobs with GIT_FILEMODE_BLOB always instead of being
at the mercy to the filesystem driver to report executable or not.
This means that if "core.filemode" lies and claims that filemode
is not supported, then we will ignore the executable bit from the
filesystem. Previously we would have allowed it.
This adds an option to the new git_repository_reset_filesystem to
recurse through submodules if desired. There may be other types
of APIs that would like a "recurse submodules" option, but this
one is particularly useful.
This also has a number of cleanups, etc., for related things
including trying to give better error messages when problems come
up from the filesystem. For example, the FAT filesystem driver on
MacOS appears to return errno EINVAL if you attempt to write a
filename with invalid UTF-8 in it. We try to capture that with a
better error message now.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Unfortunately git-core uses the term "unborn branch" and "orphan
branch" interchangeably. However, "orphan" is only really there for
the checkout command, which has the `--orphan` option so it doesn't
actually create the branch.
Branches never have parents, so the distinction of a branch with no
parents is odd to begin with. Crucially, the error messages deal with
unborn branches, so let's use that.
|
| | | |
|
| |\ \
| | |
| | | |
Thread safety for the refdb_fs
|
| | | | |
|
| | |/
| |
| |
| |
| |
| | |
If there were symbolic refs among the loose refs then the code
to create packed-refs would fail trying to parse the OID out of
them (where Git just skips trying to pack them). This fixes it.
|
| |/ |
|
| | |
|
| |
|
|
| |
Fix #1722
|
| |
|
|
| |
Also fixed an assert typo on nulltoken's HEAD
|
| |
|
|
|
| |
This fixes problems with missing function prototypes and 64-bit
data issues on Windows.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a significant reorganization of the diff code to break it
into a set of more clearly distinct files and to document the new
organization. Hopefully this will make the diff code easier to
understand and to extend.
This adds a new `git_diff_driver` object that looks of diff driver
information from the attributes and the config so that things like
function content in diff headers can be provided. The full driver
spec is not implemented in the commit - this is focused on the
reorganization of the code and putting the driver hooks in place.
This also removes a few #includes from src/repository.h that were
overbroad, but as a result required extra #includes in a variety
of places since including src/repository.h no longer results in
pulling in the whole world.
|
| |\
| |
| | |
Breaking RefDB changes
|
| | | |
|
| |\ \
| |/
|/| |
Introduce git_reference_shorthand
|
| | |
| |
| |
| | |
Generate a shorthand name out of the full refname.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Expose a way to retrieve, along with the target git_object, the reference
pointed at by some revparse expression (`@{<-n>}` or
`<branchname>@{upstream}` syntax).
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
There was a problem found in the Rugged test suite where the
refdb_fs_backend__next function could exit too early in some
very specific hashing patterns for packed refs. This ports
the Rugged test to libgit2 and then fixes the bug.
|
| |\ \
| | |
| | | |
Introduce a refs iterator
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Nobody should ever be using anything other than ALL at this level, so
remove the option altogether.
As part of this, git_reference_foreach_glob is now implemented in the
frontend using an iterator. Backends will later regain the ability of
doing the glob filtering in the backend.
|
| | | |
| | |
| | |
| | |
| | | |
Selecting wether to list loose or packed references is not something
we want to support anymore, so remove a test for this.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This allows us to get a list of reference names in a loop instead of callbacks.
|
| | |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently git_branch_set_upstream when passed a local branch
creates invalid configuration, for ex. if we setup branch
'tracking_master' to track local 'master' libgit2 generates
the following config
```
[branch "track_master"]
remote = .
merge = .refs/heads/track_master
```
The merge value is invalid and calling git_branch_upstream on
'tracking_master' results in invalid reference error.
It should do:
```
[branch "track_master"]
remote = .
merge = refs/heads/master
```
|
| |\ \
| |/
|/| |
Make sure error messages are set for most error returns
|
| | |
| |
| |
| |
| | |
There were a couple of places where an error was being returned
from branch related code but no error message was being set.
|
| |/
|
|
|
|
| |
Older versions of git would only write peeled entries for
items under refs/tags/. Newer versions will write them for
all refs, and we should be prepared to handle that.
|
| |
|
|
|
|
|
|
| |
Introduce git_remote_{fetch,push}_refspecs() to get a list of refspecs
from the remote and rename the refspec-adding functions to a less
silly name.
Use this instead of the vector index hacks in the tests.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
A remote can have a multitude of refspecs. Up to now our git_remote's
have supported a single one for each fetch and push out of simplicity
to get something working.
Let the remotes and internal code know about multiple remotes and get
the tests passing with them.
Instead of setting a refspec, the external users can clear all and add
refspecs. This should be enough for most uses, though we're still
missing a querying function.
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
This will probably prevent many lookup/free
operations in calling code.
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Branch upstream configuration
|
