summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonas Smedegaard <dr@jones.dk>2007-10-23 18:51:54 +0200
committerJonas Smedegaard <dr@jones.dk>2007-10-23 18:51:54 +0200
commitae68052e87dad54b16a9878f98dd9a2207bb9cb1 (patch)
tree2c89e283de1762968393af83c14de16f5b5c3da7
parentd6cddc84f5e916c468bf54f9519b2617b6676afc (diff)
More details on creating public repository.
-rw-r--r--README12
1 files changed, 9 insertions, 3 deletions
diff --git a/README b/README
index f94aedc..0ae879c 100644
--- a/README
+++ b/README
@@ -29,12 +29,18 @@ Pull it like this:
git clone http://source.jones.dk/ikiwiki.git
-To publish your own forked repository through web, you need to create a special
-public repository that you "push" your changes into from your private working
-repository (the --all option is rewuired only initially) - like this:
+To publish your own forked repository through web, you first need to create a
+special public repository that you "push" your changes into from your private
+working repository - like this:
GIT_DIR=public_dir/repository_name.git git --bare init --shared
chmod +x public_dir/repository_name.git/hooks/post-update
+
+To actually use your newly created public repository as above, you first need
+to populate it with your current working repository (the --all option is only
+this once, not on subsequent pushes) - like this:
+
+ git remote add origin git-reference-to-public-repository
git push --all
To resyncronize an older fork of the repository, re-applying local changes on