* martin f krafft <madduck@madduck.net> [070830 15:25]:
quoted text
> [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/
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html