user/sven/git.git/tree.c, branch v1.0rc1

[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

[PATCH] Anal retentive 'const unsigned char *sha1'

2005-06-08T20:04:53Z

Make 'sha1' parameters const where possible Signed-off-by: Jason McMullan Signed-off-by: Linus Torvalds

[PATCH] Rewrite ls-tree to behave more like "/bin/ls -a"

2005-05-29T18:40:40Z

This is a complete rewrite of ls-tree to make it behave more like what "/bin/ls -a" does in the current working directory. Namely, the changes are: - Unlike the old ls-tree behaviour that used paths arguments to restrict output (not that it worked as intended---as pointed out in the mailing list discussion, it was quite incoherent), this rewrite uses paths arguments to specify what to show. - Without arguments, it implicitly uses the root level as its sole argument ("/bin/ls -a" behaves as if "." is given without argument). - Without -r (recursive) flag, it shows the named blob (either file or symlink), or the named tree and its immediate children. - With -r flag, it shows the named path, and recursively descends into it if it is a tree. - With -d flag, it shows the named path and does not show its children even if the path is a tree, nor descends into it recursively. This is still request-for-comments patch. There is no mailing list consensus that this proposed new behaviour is a good one. The patch to t/t3100-ls-tree-restrict.sh illustrates user-visible behaviour changes. Namely: * "git-ls-tree $tree path1 path0" lists path1 first and then path0. It used to use paths as an output restrictor and showed output in cache entry order (i.e. path0 first and then path1) regardless of the order of paths arguments. * "git-ls-tree $tree path2" lists path2 and its immediate children but having explicit paths argument does not imply recursive behaviour anymore, hence paths/baz is shown but not paths/baz/b. Signed-off-by: Junio C Hamano Signed-off-by: Linus Torvalds

[PATCH] delta check

2005-05-20T22:41:45Z

This adds knowledge of delta objects to fsck-cache and various object parsing code. A new switch to git-fsck-cache is provided to display the maximum delta depth found in a repository. Signed-off-by: Nicolas Pitre Signed-off-by: Linus Torvalds

[PATCH] read_tree_recursive(): Fix leaks

2005-05-11T20:47:46Z

Fix two potential leaks. Signed-off-by: Jonas Fonseca Signed-off-by: Petr Baudis

Add git-update-cache --replace option.

2005-05-08T04:55:21Z

When "path" exists as a file or a symlink in the index, an attempt to add "path/file" is refused because it results in file vs directory conflict. Similarly when "path/file1", "path/file2", etc. exist, an attempt to add "path" as a file or a symlink is refused. With git-update-cache --replace, these existing entries that conflict with the entry being added are automatically removed from the cache, with warning messages. Signed-off-by: Junio C Hamano