Thank you very much. For skimmers the solution is : git update-server-info every time I do something to the remote repo. The reason I need http is slightly convoluted. The remote machine is shared hosting with 1 ssh login that I don't want to give to my partner AND I don't have root on that box. And as you correctly guessed, that box doesn't have the git demon. The local machine where he is doing his development. The only solution I saw without giving him my username + pass to SSH was to do http cloning. Any better solutions? Thanks guys, a great first intro to the git community. Paul Tarjan On Fri, May 29, 2009 at 6:52 AM, Jeff King <peff@xxxxxxxx> wrote: > On Fri, May 29, 2009 at 06:44:26AM -0700, Jakub Narebski wrote: > >> > Usually such a repo is bare, and gets updates only by push. In that >> > case, enabling the update hook to run update-server-info is sufficient. >> > But in your case, you are actually working on the remote repo via commit >> > and other means, so there is no convenient way to always >> > update-server-info after a change. >> >> Well, he can always add git-update-server-info to post-commit hook. > > That covers committing, but what about reset, rebase, "branch -f", etc? > I don't think there is a catch-all for all the ways that a repo can be > updated locally. > >> > Is there a particular reason you cloned over http instead of over ssh? >> Or git protocol? > > Yes, that would work fine, too. I mentioned ssh because he already > indicated that he was able to ssh into the box (and may or may not have > the git daemon set up). > > -Peff > -- 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