| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
When examining the working directory and determining whether it's
up-to-date, only consider the nanoseconds in the index entry when
built with `GIT_USE_NSEC`. This prevents us from believing that
the working directory is always dirty when the index was originally
written with a git client that uinderstands nsecs (like git 2.x).
|
|\ \
| |/
|/| |
Fix <0 unsigned comparison (stat.st_size should be an off_t)
|
| | |
|
|\ \
| | |
| | | |
Stat fixes
|
| |/ |
|
|/
|
|
| |
These are not quite like their plain counterparts and require special handling.
|
|\
| |
| | |
Racy fixes for writing new indexes
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Ensure that `git_index_read_index` clears the uptodate bit on
files that it modifies.
Further, do not propagate the cache from an on-disk index into
another on-disk index. Although this should not be done, as
`git_index_read_index` is used to bring an in-memory index into
another index (that may or may not be on-disk), ensure that we do
not accidentally bring in these bits when misused.
|
| |
| |
| |
| |
| |
| | |
The uptodate bit should have a lifecycle of a single read->write
on the index. Once the index is written, the files within it should
be scanned for racy timestamps against the new index timestamp.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Keep track of entries that we believe are up-to-date, because we
added the index entries since the index was loaded. This prevents
us from unnecessarily examining files that we wrote during the
cleanup of racy entries (when we smudge racily clean files that have
a timestamp newer than or equal to the index's timestamp when we
read it). Without keeping track of this, we would examine every
file that we just checked out for raciness, since all their timestamps
would be newer than the index's timestamp.
|
| |
| |
| |
| |
| |
| | |
When examining paths that are racily clean, do a single index->workdir
diff over the entirety of the racily clean files, instead of a diff
per file.
|
|/
|
|
|
|
| |
Allow users to set the `git_libgit2_opts` search path for the
`GIT_CONFIG_LEVEL_PROGRAMDATA`. Convert `GIT_CONFIG_LEVEL_PROGRAMDATA`
to `GIT_SYSDIR_PROGRAMDATA` for setting the configuration.
|
| |
|
|\
| |
| | |
git_index_entry__init_from_stat: set nsec fields in entry stats
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This allows us to remove OS checks from source code, instead relying
on CMake to detect whether or not `struct stat` has the nanoseconds
members we rely on.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Improve error messages when dirs prevent ref/reflog creation
|
| | | |
| | | |
| | | |
| | | |
| | | | |
When a non-empty directory exists and prevents the creation of a
reflog, provide a more informative error message.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
When a (non-empty) directory exists at the reference target
location, complain with a more actionable error message.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When creating a filebuf, detect a directory that exists in our
target file location. This prevents a failure later, when we try
to move the lock file to the destination.
|
|\ \ \ \
| | | | |
| | | | | |
Support setting custom user-agent
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We also keep the "git/1.0" prefix in order to maintain compatibility
with hosters.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We still prefix it with "git/1.0" since that's required in many
situations, but we replace the area which mentions libgit2.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When we insert a conflict in a case-insensitive index, accept the
new entry's path as the correct case instead of leaving the path we
already had.
This puts `git_index_conflict_add()` on the same level as
`git_index_add()` in this respect.
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
When we're at offset 'i', we're dealing with the 'i+1' stage, since
conflicts start at 1.
|
|\ \ \ \
| | | | |
| | | | | |
Diff: Honor `core.symlinks=false` and fake symlinks
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
On platforms that lack `core.symlinks`, we should not go looking for
symbolic links and `p_readlink` their target. Instead, we should
examine the file's contents.
|
|\ \ \ \
| | | | |
| | | | | |
Handle submodules with paths in `git_submodule_update`
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Reload the HEAD and index data for a submodule after reading the
configuration. The configuration may specify a `path`, so we must
update HEAD and index data with that path in mind.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
stream: allow registering a user-provided TLS constructor
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This allows the application to use their own TLS stream, regardless of
the capabilities of libgit2 itself.
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | | |
whitespace. Collapse spaces around newlines for the summary.
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Use checksums to detect config file changes
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reduces the chances of a crash in the thread tests. This shouldn't
affect general usage too much, since the main usage of these functions
are to read into an empty buffer.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Instead of relying on the size and timestamp, which can hide changes
performed in the same second, hash the file content's when we care about
detecting changes.
|
| | | | |
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
index: read_index must update hashes
|