From: Josh Triplett <josh@joshtriplett.org> To: git@vger.kernel.org Subject: upload-pack/ls-remote: showing non-HEAD symbolic refs? Date: Tue, 16 Aug 2016 09:18:39 -0700 Message-ID: <20160816161838.klvjhhoxsftvkfmd@x> (raw) Commit 5e7dcad771cb873e278a0571b46910d7c32e2f6c in September 2013 added support to upload-pack to show the symbolic target of non-HEAD symbolic refs. However, commit d007dbf7d6d647dbcf0f357545f43f36dec46f3b in November 2013 reverted that, because it used a capability to transmit the information, and capabilities have a limited size (limited by the pkt-line format which can't send lines longer than 64k) and can't transmit an arbitrary number of symrefs. (Incidentally, couldn't the same problem occur if the HEAD points to a long enough path to exceed 64k? Unlikely to arise in practice, but theoretically possible for a constructed repository. Not a major problem at the moment, since send-pack doesn't seem to support *sending* symbolic refs, but it would become a problem given any mechanism to send symbolic refs to the server.) I'd like to be able to see the targets of non-HEAD symbolic refs for a repository (symbolic refs under refs/). I'm interested in extending upload-pack to expose those somehow. What seems like a sensible format to do so? Would it make sense to advertise a new capability for symbolic ref targets, which would allow the client to send back a dedicated request for the targets of all symrefs? - Josh Triplett
next reply other threads:[~2016-08-16 16:20 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-08-16 16:18 Josh Triplett [this message] 2016-08-16 16:31 ` Jeff King 2016-08-16 17:34 ` Josh Triplett 2016-08-16 18:28 ` Jeff King 2016-08-16 18:50 ` Stefan Beller 2016-08-16 20:34 ` Josh Triplett 2016-08-16 20:31 ` Josh Triplett 2016-08-16 20:54 ` Jeff King 2016-08-16 21:11 ` Josh Triplett 2016-08-16 21:15 ` Jeff King 2016-08-16 22:24 ` Josh Triplett 2016-08-19 13:47 ` Jeff King
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20160816161838.klvjhhoxsftvkfmd@x \ --to=josh@joshtriplett.org \ --cc=git@vger.kernel.org \ --subject='Re: upload-pack/ls-remote: showing non-HEAD symbolic refs?' \ /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
git@vger.kernel.org list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ git@vger.kernel.org public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git