aboutsummaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-11-21 13:42:55 -0800
committerJunio C Hamano <junkio@cox.net>2005-11-21 13:42:55 -0800
commitaa7f412abf605d824c7f72dbfaedd27d5429a025 (patch)
tree414f0f15131cae4e186f920ebc426fa5fa86b4d2 /Documentation
parent9f70b806920e3ea158d7e189a1ec668445c13359 (diff)
downloadgit-aa7f412abf605d824c7f72dbfaedd27d5429a025.tar.gz
git-aa7f412abf605d824c7f72dbfaedd27d5429a025.tar.xz
tutorial: setting up a tree for subsystem maintainers
The "copying over packs" step is to prevent the objects available in upstream repository to get expanted in the subsystem maintainer tree, and is still valid if the upstream repository do not live on the same machine. But if they are on the same machine using objects/info/alternates is cleaner. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/tutorial.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 03eb4216f..e2dfb00ab 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -1534,7 +1534,10 @@ on that project and has an own "public repository" goes like this:
the "project lead" person does.
3. Copy over the packed files from "project lead" public
- repository to your public repository.
+ repository to your public repository, unless the "project
+ lead" repository lives on the same machine as yours. In the
+ latter case, you can use `objects/info/alternates` file to
+ point at the repository you are borrowing from.
4. Push into the public repository from your primary
repository. Run `git repack`, and possibly `git prune` if the