Re: How to create and keep up to date a naked/bare repository?

From: Mathieu Chouquet-Stringer <ml2news@free.fr>
Date: Jan 27, 2006, 13:34 UTC
Message-ID: <m34q3p7q1n.fsf@localhost.localdomain>
In-Reply-To: <7vd5ie735a.fsf@assigned-by-dhcp.cox.net>

Thanks and sorry for making you write this long message...

junkio@cox.net (Junio C Hamano) writes:

Show 7 quoted lines

> [...]
>  - A mirror of somebody else's work.
> 
>    I suspect this is what you are doing.  Instead of individual
>    developers pulling directly from upstream, you would want to
>    fetch and update the bare cloned repository and have your
>    developers fetch from it.

Correct.

Show 28 quoted lines

> Let's outline how.
> 
> What I would suggest is to arrange things like this:
> 
>    +-------------------------------------------+
>    | Your upstream repository                  |
>    | git://git.kernel.org/pub/scm/git/git.git/ |
>    +-------------------------------------------+ 
>       |                                      ^
>       | (1)                                  | (5)
>       |                                      |
>       v                                      |
>    +-----------------+                     +----------------+
>    | Your central    |        (4)          | My development |
>    | bare repository |-------------------->| tree           |
>    +-----------------+                     +----------------+
>       |      ^
>       | (2)  | (3)
>       |      |
>       v      |
>    +------------------+
>    | Your developers' |+
>    | trees            ||+
>    +------------------+||
>      +-----------------+|
>       +-----------------+
> [...]
> Does this make sense now?

It totally does. I guess this email could end up in the Documentation folder in some way!?

-- 
Mathieu Chouquet-Stringer
    "Le disparu, si l'on vénère sa mémoire, est plus présent et
                 plus puissant que le vivant".
           -- Antoine de Saint-Exupéry, Citadelle --