delta/libgit2.git/src/tree.c, branch v0.3.0

Git does not like zero padded file attributes (git fsck)

2011-02-07T05:11:17+00:00

Further correction to tree entry sorting (for git fsck)

2011-02-07T05:11:00+00:00

Fixes a Win32/MSVC compilation issue.

2011-02-05T14:03:48+00:00

Keep the tree entries always internally sorted

2011-02-05T07:11:17+00:00

Don't allow access to any tree entries whilst the entries array is
unsorted. We keep track on when the array is unsorted, and any methods
that access the array while it is unsorted now sort the array before
accessing it.

Signed-off-by: Vicent Marti

Use Git's own tree entry sorting algorithm

2011-02-03T06:47:26+00:00

If plain strcmp is used, as this code did before, the final sorting may
end up different from what git-add would do (for example, 'boost'
appearing before 'boost-build.jam', because Git sorts as if it were
spelled 'boost/').

If the sorting is incorrect like this, Git 1.7.4 insists that unmodified
files have been modified.  For example, my test repository has these
four entries:

drwxr-xr-x  199 johnw  wheel   6766 Feb  2 17:21 boost
-rw-r--r--    1 johnw  wheel    849 Feb  2 17:22 boost-build.jam
-rw-r--r--    1 johnw  wheel    989 Feb  2 17:21 boost.css
-rw-r--r--    1 johnw  wheel   6308 Feb  2 17:21 boost.png

Here is the output from git-ls-tree for these files, in a commit tree
created using git-add and git-commit:

100644 blob 8b8775433aef73e9e12609610ae2e35cf1e7ec2c    boost-build.jam
100644 blob 986c4050fa96d825a1311c8e871cdcc9a3e0d2c3    boost.css
100644 blob b4d51fcd5c9149fd77f5ca6ed2b6b1b70e8fe24f    boost.png
040000 tree 46537eeaa4d577010f19b1c9e940cae9a670ff5c    boost

Here is the output for the same commit produced using libgit2:

040000 tree c27c0fd1436f28a6ba99acd0a6c17d178ed58288	boost
100644 blob 8b8775433aef73e9e12609610ae2e35cf1e7ec2c	boost-build.jam
100644 blob 986c4050fa96d825a1311c8e871cdcc9a3e0d2c3	boost.css
100644 blob b4d51fcd5c9149fd77f5ca6ed2b6b1b70e8fe24f	boost.png

Due to this reordering, git-status claims the three blobs are always
modified, no matter what I do using git-read-tree or git-reset or
git-checkout to update the index.

Make git_tree_clear_entries visible to the user

2011-02-01T10:04:49+00:00

Added git_tree_add_entry_unsorted and git_tree_sort_entries

2011-02-01T10:04:43+00:00

Return the created entry in git_tree_add_entry()

2011-01-29T00:12:59+00:00

Yes, we are breaking the API. Alpha software, deal with it.

We need a way of getting a pointer to each newly added entry to the
index, because manually looking up the entry after creation is
outrageously expensive.

Signed-off-by: Vicent Marti

Fix initialization of in-memory trees

2011-01-20T22:43:27+00:00

In-memory tree objects were not being properly initialized, because the
internal entries vector was created on the 'parse' method.

Signed-off-by: Vicent Marti

Change the library include file

2010-12-06T21:03:16+00:00

Libgit2 is now officially include as

	#include ""

or indidividual files may be included as

	#include 

Signed-off-by: Vicent Marti