summaryrefslogtreecommitdiff
path: root/t/t5000-tar-tree.sh
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2006-04-26 08:20:50 (GMT)
committerJunio C Hamano <junkio@cox.net>2006-05-02 05:29:16 (GMT)
commit6bd20358a9b831b3b545284188871bc844245c25 (patch)
tree421b2749edc4442cda4f455e8c157a229f287ad9 /t/t5000-tar-tree.sh
parentf4c6f2d328e2f30ad63fdfca26a5e4a11cef35bf (diff)
downloadgit-6bd20358a9b831b3b545284188871bc844245c25.zip
git-6bd20358a9b831b3b545284188871bc844245c25.tar.gz
git-6bd20358a9b831b3b545284188871bc844245c25.tar.bz2
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>
Diffstat (limited to 't/t5000-tar-tree.sh')
0 files changed, 0 insertions, 0 deletions