From: Jeff King <peff@peff.net> To: git@vger.kernel.org Cc: Jon Simons <jon@jonsimons.org> Subject: [PATCH 0/2] ls-remote and v2 ref prefixes Date: Wed, 31 Oct 2018 00:23:18 -0400 [thread overview] Message-ID: <20181031042318.GA5347@sigill.intra.peff.net> (raw) This series fixes a bug where ls-remote sends a ref-advertisement prefix when it shouldn't, and then optimizes a spot where it doesn't send one but could. [1/2]: ls-remote: do not send ref prefixes for patterns [2/2]: ls-remote: pass heads/tags prefixes to transport builtin/ls-remote.c | 13 +++++-------- t/t5512-ls-remote.sh | 18 ++++++++++++++++++ 2 files changed, 23 insertions(+), 8 deletions(-) -Peff
next reply other threads:[~2018-10-31 4:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-31 4:23 Jeff King [this message] 2018-10-31 4:24 ` [PATCH 1/2] ls-remote: do not send ref prefixes for patterns Jeff King 2018-10-31 4:37 ` Junio C Hamano 2018-11-08 20:52 ` Jonathan Tan 2018-10-31 4:24 ` [PATCH 2/2] ls-remote: pass heads/tags prefixes to transport 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=20181031042318.GA5347@sigill.intra.peff.net \ --to=peff@peff.net \ --cc=git@vger.kernel.org \ --cc=jon@jonsimons.org \ --subject='Re: [PATCH 0/2] ls-remote and v2 ref prefixes' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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 read-only IMAP folder(s) and NNTP newsgroup(s).