technical/shallow: stop referring to grafts
Now that grafts are deprecated, we should start to assume that readers have no idea what grafts are. So it makes more sense to make the description of the "shallow" feature stand on its own. Suggested-by: Eric Sunshine <sunshine@sunshineco.com> Helped-by: Junio Hamano <gitster@pobox.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Johannes Schindelin committed
Apr 29, 2018 at 00:45 UTC
8d0d81a9caf612b479b96bc474815e2f38c4746b
1 file changed
+4
-9
Documentation/technical/shallow.txt
+4
-9
@@ -8,15 +8,10 @@ repo, and therefore grafts are introduced pretending that
8
these commits have no parents.
9
*********************************************************
10
11
-The basic idea is to write the SHA-1s of shallow commits into
12
-$GIT_DIR/shallow, and handle its contents like the contents
13
-of $GIT_DIR/info/grafts (with the difference that shallow
14
-cannot contain parent information).
15
-
16
-This information is stored in a new file instead of grafts, or
17
-even the config, since the user should not touch that file
18
-at all (even throughout development of the shallow clone, it
19
-was never manually edited!).
11
+$GIT_DIR/shallow lists commit object names and tells Git to
12
+pretend as if they are root commits (e.g. "git log" traversal
13
+stops after showing them; "git fsck" does not complain saying
14
+the commits listed on their "parent" lines do not exist).
15
16
Each line contains exactly one SHA-1. When read, a commit_graft
17
will be constructed, which has nr_parent < 0 to make it easier