From: Jeff King <peff@peff.net>
To: Michael Tyson <michael@atastypixel.com>
Cc: git@vger.kernel.org
Subject: Re: Cloning remote HTTP repository: Can only see 'master' branch
Date: Tue, 29 Jan 2013 03:23:17 -0500 [thread overview]
Message-ID: <20130129082317.GA6396@sigill.intra.peff.net> (raw)
In-Reply-To: <83605E83-1110-449B-969D-AB43158376EA@atastypixel.com>
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
next prev parent reply other threads:[~2013-01-29 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 5:54 Cloning remote HTTP repository: Can only see 'master' branch Michael Tyson
2013-01-29 8:23 ` Jeff King [this message]
2013-01-30 0:06 ` Michael Tyson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130129082317.GA6396@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=michael@atastypixel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).