Oliver Kullmann wrote:
I have the following problem: We use a public repository, a bare repository A, used with push and pull via ssh. A is only to be used by the core developer group. Now I want to create another public repository B, from which anonymous pull is possible via http. So B should be another bare repository. The problem is now that it seems not to be possible to update B: 1. pulling from A is not possible since B is bare; 2. fetching from A seems to work, checking the content of B via gitk seems to indicate that B has been updated --- however pulling from B doesn't work: The newly fetched changes are not transported to a repository which pulls from B ???
Probably in your setup, B is tracking A as a remote and if you fetch, only those remotes are updated, but not the local branches in B. If you then clone from B, you don't get B's remotes, you get B's branches. You probably want to do this: path/to/B$ git remote rm origin path/to/B$ git remote add --mirror origin path/to/A Though, I wonder if it makes sense to have a 'git clone --bare' set up the remote in mirror mode by default. I'm unsure of what use remotes are in a bare repo. jlh -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
