From 248da9a6903668638a2b8416f8e12322649d4403 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Tue, 10 Nov 2009 10:10:31 +0100 Subject: [PATCH] README: Describe forks --- README | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README b/README index dbf4b64..a32b20c 100644 --- a/README +++ b/README @@ -107,6 +107,18 @@ And another year later, Pasky finally finished the job by porting Girocco back to useable state for repo.or.cz and further cleaning it up. +Forks +----- + +An important Girocco concept is a _project fork_ - anyone can fork any +project (including a fork of another project), the fork resides in the +directory structure as PARENT/FORK.git. Forks are meant as a place for +people to freely publish their modifications for the project, even if +they don't have push permissions to the parent. To save space and +bandwidth, the fork will reuse objects in the parent project, garbage +collection is done in a clever way not to prune objects used in forks. + + Implementation of project database ---------------------------------- -- 2.11.4.GIT