4 Коммитов

Автор	SHA1	Сообщение	Дата
Alexandre Julliard	d64d6c9fc7	get_shallow_commits: Avoid memory leak if a commit has been reached already. ... Signed-off-by: Alexandre Julliard <julliard@winehq.org> Signed-off-by: Junio C Hamano <junkio@cox.net>	2006-11-24 15:42:50 -08:00
Alexandre Julliard	abef3a1625	Shallow clone: do not ignore shallowness when following tags ... 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 <junkio@cox.net>	2006-11-24 15:42:49 -08:00
Johannes Schindelin	f53514bc2d	allow deepening of a shallow repository ... Now, by saying "git fetch -depth <n> <repo>" you can deepen a shallow repository. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <junkio@cox.net>	2006-11-24 15:42:49 -08:00
Johannes Schindelin	ed09aef06f	support fetching into a shallow repository ... 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 <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <junkio@cox.net>	2006-11-24 15:42:49 -08:00