| commit | ed09aef06fda2ba06a7412e3fa43ab1c3449f723 | |
| author | Johannes Schindelin <Johannes.Schindelin@gmx.de> | |
| Mon, 30 Oct 2006 19:09:06 +0000 (30 20:09 +0100) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Fri, 24 Nov 2006 23:42:49 +0000 (24 15:42 -0800) | ||
| tree | ae3de15cc0743c919e541f56a96082cf6c0b7cc8 | treesnapshot (tar.gz zip) |
| parent | 9b8dc263e1b0d470cc67a824837d8884ae3e7136 | commitdiff |
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>
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>