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>
Junio C Hamano committed
Nov 21, 2005 at 13:42 UTC
aa7f412abf605d824c7f72dbfaedd27d5429a025
1 file changed
+4
-1
Documentation/tutorial.txt
+4
-1
@@ -1534,7 +1534,10 @@ on that project and has an own "public repository" goes like this:
1534
the "project lead" person does.
1535
1536
3. Copy over the packed files from "project lead" public
1537
- repository to your public repository.
1537
+ repository to your public repository, unless the "project
1538
+ lead" repository lives on the same machine as yours. In the
1539
+ latter case, you can use `objects/info/alternates` file to
1540
+ point at the repository you are borrowing from.
1541
1542
4. Push into the public repository from your primary
1543
repository. Run `git repack`, and possibly `git prune` if the