git/tree.c, branch v1.2.2

Only use a single parser for tree objects

2006-01-26T09:08:29Z

This makes read_tree_recursive and read_tree take a struct tree instead of a buffer. It also move the declaration of read_tree into tree.h (where struct tree is defined), and updates ls-tree and diff-index (the only places that presently use read_tree*()) to use the new versions. Signed-off-by: Daniel Barkalow Signed-off-by: Junio C Hamano

[PATCH] Compilation: zero-length array declaration.

2006-01-07T18:51:06Z

ISO C99 (and GCC 3.x or later) lets you write a flexible array at the end of a structure, like this: struct frotz { int xyzzy; char nitfol[]; /* more */ }; GCC 2.95 and 2.96 let you to do this with "char nitfol[0]"; unfortunately this is not allowed by ISO C90. This declares such construct like this: struct frotz { int xyzzy; char nitfol[FLEX_ARRAY]; /* more */ }; and git-compat-util.h defines FLEX_ARRAY to 0 for gcc 2.95 and empty for others. If you are using a C90 C compiler, you should be able to override this with CFLAGS=-DFLEX_ARRAY=1 from the command line of "make". Signed-off-by: Junio C Hamano

struct tree: remove unused field "parent"

2005-12-05T07:19:31Z

The field is not used anymore, after the recent ls-tree rewrite. Signed-off-by: Junio C Hamano

ls-tree: major rewrite to do pathspec

2005-11-29T07:00:14Z

git-ls-tree should be rewritten to use a pathspec the same way everybody else does. Right now it's the odd man out: if you do git-ls-tree HEAD divers/char drivers/ it will show the same files _twice_, which is not how pathspecs in general work. How about this patch? It breaks some of the git-ls-tree tests, but it makes git-ls-tree work a lot more like other git pathspec commands, and it removes more than 150 lines by re-using the recursive tree traversal (but the "-d" flag is gone for good, so I'm not pushing this too hard). Linus

Rework object refs tracking to reduce memory usage

2005-11-15T19:42:29Z

Store pointers to referenced objects in a variable sized array instead of linked list. This cuts down memory usage of utilities which use object references; e.g., git-fsck-objects --full on the git.git repository consumes about 2 MB of memory tracked by Massif instead of 7 MB before the change. Object refs are still the biggest consumer of memory (57%), but the malloc overhead for a single block instead of a linked list is substantially smaller. Signed-off-by: Sergey Vlasov Signed-off-by: Junio C Hamano

[PATCH] Add a function for getting a struct tree for an ent.

2005-09-11T01:27:40Z

Signed-off-by: Daniel Barkalow Signed-off-by: Junio C Hamano

git-fsck-cache: be stricter about "tree" objects

2005-07-28T01:57:14Z

In particular, warn about things like zero-padding of the mode bits, which is a big no-no, since it makes otherwise identical trees have different representations (and thus different SHA1 numbers). Also make the warnings more regular. Signed-off-by: Linus Torvalds

Fix up read_tree() pathspec matching to use "const char **"

2005-07-14T18:39:27Z

The same way the other pathspecs work. Also fix missing success return from the matching - not that anything actually uses this yet ;)

Start adding interfaces to read in partial trees

2005-07-14T18:26:31Z

The same way "git-diff-tree" can limit its output to just a set of matches, we can read in just a partial tree for comparison purposes.

[PATCH] Fix oversimplified optimization for add_cache_entry().

2005-06-25T23:52:16Z

An earlier change to optimize directory-file conflict check broke what "read-tree --emu23" expects. This is fixed by this commit. (1) Introduces an explicit flag to tell add_cache_entry() not to check for conflicts and use it when reading an existing tree into an empty stage --- by definition this case can never introduce such conflicts. (2) Makes read-cache.c:has_file_name() and read-cache.c:has_dir_name() aware of the cache stages, and flag conflict only with paths in the same stage. Signed-off-by: Junio C Hamano Signed-off-by: Linus Torvalds