diff options
author | Johannes Schindelin <Johannes.Schindelin@gmx.de> | 2006-10-30 22:09:06 +0300 |
---|---|---|
committer | Junio C Hamano <junkio@cox.net> | 2006-11-25 02:42:49 +0300 |
commit | ed09aef06fda2ba06a7412e3fa43ab1c3449f723 (patch) | |
tree | ae3de15cc0743c919e541f56a96082cf6c0b7cc8 /Makefile | |
parent | 9b8dc263e1b0d470cc67a824837d8884ae3e7136 (diff) |
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>
Diffstat (limited to 'Makefile')
-rw-r--r-- | Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -260,7 +260,7 @@ LIB_OBJS = \ revision.o pager.o tree-walk.o xdiff-interface.o \ write_or_die.o trace.o list-objects.o grep.o \ alloc.o merge-file.o path-list.o help.o unpack-trees.o $(DIFF_OBJS) \ - color.o wt-status.o archive-zip.o archive-tar.o + color.o wt-status.o archive-zip.o archive-tar.o shallow.o BUILTIN_OBJS = \ builtin-add.o \ |