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