Ah! Lovely, thank you, Jeff! Alas, it's a shared server so I'm limited to what the host provides, but that solves my problem. Cheers! On 29 Jan 2013, at 19:23, Jeff King <peff@xxxxxxxx> wrote: > On Tue, Jan 29, 2013 at 04:54:13PM +1100, Michael Tyson wrote: > >> I've a readonly git repository that I'm hosting via HTTP (a bare git >> repository located within the appropriate directory on the server). I >> push to it via my own SSH account (local repository with a remote >> pointing to the ssh:// URL). >> >> This has all worked fine so far - I push via ssh, and others can clone >> and pull via the HTTP URL. >> >> I've recently added a branch - "beta" - which pushed just fine, but >> now cloning via the HTTP URL doesn't seem to show the new branch - >> just master: > > If you are using the "dumb" http protocol (i.e., the web server knows > nothing about git, and just serves the repo files), you need to run "git > update-server-info" after each push in order to update the static file > that tells the git client about each ref. You can have git do it > automatically for you by setting receive.updateServerInfo in the server > repo's config. > > If the server is yours to control, consider setting up the "smart" http > protocol, as it is much more efficient. Details are in "git help > http-backend". > > -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 -- 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