user/sven/git.git/shallow.c, branch v1.8.0.2

object.h: Add OBJECT_ARRAY_INIT macro and make use of it.

2010-08-30T05:42:49Z

Signed-off-by: Thiago Farina Signed-off-by: Junio C Hamano

Merge branch 'mk/maint-parse-careful'

2008-02-19T04:56:01Z

* mk/maint-parse-careful: peel_onion: handle NULL check return value from parse_commit() in various functions parse_commit: don't fail, if object is NULL revision.c: handle tag->tagged == NULL reachable.c::process_tree/blob: check for NULL process_tag: handle tag->tagged == NULL check results of parse_commit in merge_bases list-objects.c::process_tree/blob: check for NULL reachable.c::add_one_tree: handle NULL from lookup_tree mark_blob/tree_uninteresting: check for NULL get_sha1_oneline: check return value of parse_object read_object_with_reference: don't read beyond the buffer

check return value from parse_commit() in various functions

2008-02-19T04:49:13Z

Signed-off-by: Martin Koegler Signed-off-by: Junio C Hamano

deref_tag: handle return value NULL

2008-02-18T07:46:55Z

Signed-off-by: Martin Koegler Signed-off-by: Junio C Hamano

War on whitespace

2007-06-07T07:04:01Z

This uses "git-apply --whitespace=strip" to fix whitespace errors that have crept in to our source files over time. There are a few files that need to have trailing whitespaces (most notably, test vectors). The results still passes the test, and build result in Documentation/ area is unchanged. Signed-off-by: Junio C Hamano

is_repository_shallow(): prototype fix.

2007-01-22T06:22:23Z

Signed-off-by: Junio C Hamano

get_shallow_commits: Avoid memory leak if a commit has been reached already.

2006-11-24T23:42:50Z

Signed-off-by: Alexandre Julliard Signed-off-by: Junio C Hamano

Shallow clone: do not ignore shallowness when following tags

2006-11-24T23:42:49Z

Tags should be considered when truncating the commit list. The patch below fixes it, and fetches the right number of commits for each tag. However the correct fix is probably to not fetch historical tags at all. Signed-off-by: Junio C Hamano

allow deepening of a shallow repository

2006-11-24T23:42:49Z

Now, by saying "git fetch -depth " you can deepen a shallow repository. Signed-off-by: Johannes Schindelin Signed-off-by: Junio C Hamano

support fetching into a shallow repository

2006-11-24T23:42:49Z

A shallow commit is a commit which has parents, which in turn are "grafted away", i.e. the commit appears as if it were a root. Since these shallow commits should not be edited by the user, but only by core git, they are recorded in the file $GIT_DIR/shallow. A repository containing shallow commits is called shallow. The advantage of a shallow repository is that even if the upstream contains lots of history, your local (shallow) repository needs not occupy much disk space. The disadvantage is that you might miss a merge base when pulling some remote branch. Signed-off-by: Johannes Schindelin Signed-off-by: Junio C Hamano