author | Junio C Hamano <junkio@cox.net> | |
Wed, 26 Apr 2006 08:20:50 +0000 (01:20 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Tue, 2 May 2006 05:29:16 +0000 (22:29 -0700) | ||
commit | 6bd20358a9b831b3b545284188871bc844245c25 | |
tree | 421b2749edc4442cda4f455e8c157a229f287ad9 | tree | snapshot |
parent | f4c6f2d328e2f30ad63fdfca26a5e4a11cef35bf | commit | diff |
write-tree: --prefix=<path>
The "bind" commit can express an aggregation of multiple
projects into a single commit.
In such an organization, there would be one project, root of
whose tree object is at the same level of the root of the
aggregated projects, and other projects have their toplevel in
separate subdirectories. Let's call that root level project the
"primary project", and call other ones just "subprojects".
You would first read-tree the primary project, and then graft
the subprojects under their appropriate location using read-tree
--prefix=<subdir>/ repeatedly.
To write out a tree object from such an index for a subproject,
write-tree --prefix=<subdir>/ is used.
Signed-off-by: Junio C Hamano <junkio@cox.net>
The "bind" commit can express an aggregation of multiple
projects into a single commit.
In such an organization, there would be one project, root of
whose tree object is at the same level of the root of the
aggregated projects, and other projects have their toplevel in
separate subdirectories. Let's call that root level project the
"primary project", and call other ones just "subprojects".
You would first read-tree the primary project, and then graft
the subprojects under their appropriate location using read-tree
--prefix=<subdir>/ repeatedly.
To write out a tree object from such an index for a subproject,
write-tree --prefix=<subdir>/ is used.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-write-tree.txt | diff | blob | history | |
cache-tree.c | diff | blob | history | |
cache-tree.h | diff | blob | history | |
t/t0000-basic.sh | diff | blob | history | |
write-tree.c | diff | blob | history |