From: "Julian Phillips" <jp3@quantumfyre.co.uk>
To: git@vger.kernel.org
Cc: Julian Phillips <julian@quantumfyre.co.uk>
Subject: [PATCH] Use stdin reflist passing in parse-remote
Date: Tue, 13 Feb 2007 01:21:40 +0000 [thread overview]
Message-ID: <1171329702101-git-send-email-julian@quantumfyre.co.uk> (raw)
In-Reply-To: <11713297013179-git-send-email-julian@quantumfyre.co.uk>
Use the new stdin reflist passing mechanism for the call to
fetch--tool expand-refs-wildcard, allowing passing of more
than ~128K of reflist data.
Signed-off-by: Julian Phillips <julian@quantumfyre.co.uk>
---
git-parse-remote.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-parse-remote.sh b/git-parse-remote.sh
index 9b19a21..185eb54 100755
--- a/git-parse-remote.sh
+++ b/git-parse-remote.sh
@@ -81,7 +81,7 @@ get_remote_default_refs_for_push () {
# is to help prevent randomly "globbed" ref from being chosen as
# a merge candidate
expand_refs_wildcard () {
- git fetch--tool expand-refs-wildcard "$ls_remote_result" "$@"
+ echo "$ls_remote_result" | git fetch--tool expand-refs-wildcard "-" "$@"
}
# Subroutine to canonicalize remote:local notation.
--
1.4.4.4
next prev parent reply other threads:[~2007-02-13 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 1:21 [PU PATCH] Fix git fetch for very large ref counts Julian Phillips
2007-02-13 1:21 ` [PATCH] Allow fetch--tool to read from stdin Julian Phillips
2007-02-13 1:21 ` Julian Phillips [this message]
2007-02-13 1:21 ` [PATCH] Use stdin reflist passing in git-fetch.sh Julian Phillips
2007-02-13 2:31 ` Linus Torvalds
2007-02-13 3:18 ` [PU PATCH] Fix git fetch for very large ref counts Junio C Hamano
2007-02-13 10:39 ` Julian Phillips
2007-02-13 17:58 ` Junio C Hamano
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=1171329702101-git-send-email-julian@quantumfyre.co.uk \
--to=jp3@quantumfyre.co.uk \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.