From: Bart Trojanowski <bart@jukie.net>
Date: Thu, 30 Aug 2007 20:27:47 GMT
Subject: Re: publishing a forked^W cloned directory with ancestry
Message-ID: <20070830202747.GT10772@jukie.net>
In-Reply-To: <20070830192533.GA18751@piper.oerlikon.madduck.net>

* martin f krafft <madduck@madduck.net> [070830 15:25]:
> [1] I tried cloning B from A, then cloning C from B. Within C, there
>     is no reference to A's master branch, so unless B pulled changes
>     from A and C pulled changes from B, C could not be updated.

I think a .git/config like this will do what you want:

[remote "upstream"]
        url = git://mdadm-upstream-repo
        fetch = +refs/heads/*:refs/remotes/upstream/*

[remote "debian"]
        url = git://debian-repo-you-want-to-publish-to
        fetch = +refs/heads/*:refs/remotes/debian/*
        push = refs/remotes/upstream/master:refs/heads/upstream
        push = refs/heads/master:refs/heads/master

Now when you 'git push debian' it will populate the 'upstream' and
'master' branches properly.

When someone clones your repo, they will get origin/master (your branch)
and origin/upstream (the official mdadm branch).

Did I understand the problem correctly?

-Bart

-- 
				WebSig: http://www.jukie.net/~bart/sig/