- 01 Aug, 2015 2 commits
-
-
When we pass the path of a repository to `_bypath()`, we should behave like git and stage it as a `_COMMIT` regardless of whether it is registered a a submodule.
Carlos Martín Nieto committed -
Linquize committed
-
- 12 Jul, 2015 2 commits
-
-
Similarly to how git itself does it, allow the index update operation to stage a change in a submodule's HEAD.
Carlos Martín Nieto committed -
This also affects `git_index_add_bypath()` by providing a better error message and a specific error code when a directory is passed.
Carlos Martín Nieto committed
-
- 30 Jun, 2015 1 commit
-
-
Edward Thomson committed
-
- 29 Jun, 2015 1 commit
-
-
Edward Thomson committed
-
- 26 Jun, 2015 1 commit
-
-
Carlos Martín Nieto committed
-
- 22 Jun, 2015 2 commits
-
-
Even though the file is empty and thus the size in the entry matches, we should be able to detect it as a difference.
Carlos Martín Nieto committed -
They fit there much better, even though we often check by diffing, it's about the behaviour of the index.
Carlos Martín Nieto committed
-
- 19 Jun, 2015 1 commit
-
-
This will tell us which numbers we were trying to compare, rather than just telling us that they're different.
Carlos Martín Nieto committed
-
- 02 Jun, 2015 1 commit
-
-
Pierre-Olivier Latour committed
-
- 28 May, 2015 5 commits
-
-
When confronted with a conflict in the index, `git_index_add_all` should stage the working directory copy. If there is no file in the working directory, the conflict should simply be removed.
Edward Thomson committed -
It's not always obvious the mapping between stage level and conflict-ness. More importantly, this can lead otherwise sane people to write constructs like `if (!git_index_entry_stage(entry))`, which (while technically correct) is unreadable. Provide a nice method to help avoid such messy thinking.
Edward Thomson committed -
Edward Thomson committed
-
Edward Thomson committed
-
When adding a conflict for some path, remove the staged entry. Otherwise, an illegal index (with both stage 0 and high-stage entries) would result.
Edward Thomson committed
-
- 21 May, 2015 1 commit
-
-
Edward Thomson committed
-
- 14 May, 2015 1 commit
-
-
Without this option, we would not be able to catch exec bit changes.
Carlos Martín Nieto committed
-
- 11 May, 2015 1 commit
-
-
Edward Thomson committed
-
- 21 Apr, 2015 1 commit
-
-
The idea...sometimes, a filemode is user-specified via an explicit git_index_entry. In this case, believe the user, always. Sometimes, it is instead built up by statting the file system. In those cases, go with the existing logic we have to determine whether the file system supports all filemodes and symlinks, and make the best guess. On file systems which have full filemode and symlink support, this commit should make no difference. On others (most notably Windows), this will fix problems things like: * git_index_add and git_index_add_frombuffer() should be believed. * As a consequence, git_checkout_tree should make the filemodes in the index match the ones in the tree. * And diffs with GIT_DIFF_UPDATE_INDEX don't write the wrong filemodes. * And merges, and probably other downstream stuff now fixed, too. This makes my previous changes to checkout.c unnecessary, so they are now reverted. Also, added a test for index_entry permissions from git_index_add and git_index_add_frombuffer, both of which failed before these changes.
John Fultz committed
-
- 03 Mar, 2015 2 commits
-
-
This function is meant to simulate what git does in the reset command, so we should include the reflog message in that.
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
-
- 25 Feb, 2015 1 commit
-
-
git_index_add_frombuffer enables now to store a memory buffer in the odb and to store an entry in the index directly if the index is attached to a repository.
Damien PROFETA committed
-
- 14 Feb, 2015 1 commit
-
-
Introduce `git_indexwriter`, to allow us to lock the index while performing additional operations, then complete the write (or abort, unlocking the index).
Edward Thomson committed
-
- 18 Dec, 2014 3 commits
-
-
Edward Thomson committed
-
Carlos Martín Nieto committed
-
We need these directories to exist so cl_git_mkfile() can create the files we ask it to.
Carlos Martín Nieto committed
-
- 17 Dec, 2014 1 commit
-
-
Path validation may be influenced by `core.protectHFS` and `core.protectNTFS` configuration settings, thus treebuilders can take a repository to influence their configuration.
Edward Thomson committed
-
- 16 Dec, 2014 1 commit
-
-
Vicent Marti committed
-
- 05 Dec, 2014 1 commit
-
-
Will Stamper committed
-
- 27 Oct, 2014 1 commit
-
-
Edward Thomson committed
-
- 22 Oct, 2014 1 commit
-
-
The entry_count field is the amount of index entries covered by a particular cache entry, that is how many files are there (recursively) under a particular directory. The current code that attemps to do this is severely defincient and is trying to count the amount of children, which always comes up to zero. We don't even need to recount, since we have the information during the cache creation. We can take that number and keep it, as we only ever invalidate or replace.
Carlos Martín Nieto committed
-
- 10 Oct, 2014 3 commits
-
-
If e.g. the root tree is invalidated, we still want to write out its children, since those may still have valid cache entries.
Carlos Martín Nieto committed -
Keeping the cache around after read-tree is only one part of the optimisation opportunities. In order to share the cache between program instances, we need to write the TREE extension to the index. Do so, taking the opportunity to rename 'entries' to 'entry_count' to match the name given in the format description. The included test is rather trivial, but works as a sanity check.
Carlos Martín Nieto committed -
These test that we invalidate at the right levels and that we remove the tree cache when clearing the index.
Carlos Martín Nieto committed
-
- 03 Aug, 2014 1 commit
-
-
Signed-off-by: Sven Strickroth <email@cs-ware.de>
Sven Strickroth committed
-
- 01 Jul, 2014 1 commit
-
-
Edward Thomson committed
-
- 03 Jun, 2014 1 commit
-
-
Carlos Martín Nieto committed
-
- 22 May, 2014 1 commit
-
-
Carlos Martín Nieto committed
-
- 19 May, 2014 1 commit
-
-
If you enabled core.safecrlf on an LF-ending platform, we would error even for files with all LFs. We should only be warning on irreversible mappings, I think.
Russell Belfer committed
-