From: Ivan Todoroski <grnch@gmx.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH v3 0/4] Clone fails on a repo with too many heads/tags
Date: Mon, 02 Apr 2012 17:11:17 +0200 [thread overview]
Message-ID: <4F79C195.6090905@gmx.net> (raw)
The full description of the problem can be found in the first patch.
Changes since v2:
* fix a bunch of code style and documentation issues spotted by Junio
* tighten ref format checking on stdin to not allow extra whitespace
* make fetch-pack --stdin tests independent of the order of refs
* add test for duplicate refs on stdin
* drop the two ugly and redundant --stateless-rpc tests
* drop the test that tolerated extra whitespace
Changes since the original patch:
* add test cases
* add full commit messages
* fix formatting problem in --stdin doc
* split overly long fetch_pack_usage line
* use strbuf_getline() instead of fgets() for reading refs from stdin
* minor optimization of the pkt-line reading loop, it was using xstrdup()
even though the string length was already known, use xmemdupz() instead
* rework the remote-curl.c patch to not add new parameters to rpc_service(),
instead add a new strbuf member to rpc_state to pass the info around
Ivan Todoroski (4):
fetch-pack: new --stdin option to read refs from stdin
remote-curl: send the refs to fetch-pack on stdin
fetch-pack: test cases for the new --stdin option
remote-curl: main test case for the OS command line overflow
Documentation/git-fetch-pack.txt | 10 ++++++
builtin/fetch-pack.c | 42 +++++++++++++++++++++++-
fetch-pack.h | 1 +
remote-curl.c | 14 ++++++--
t/t5500-fetch-pack.sh | 66 ++++++++++++++++++++++++++++++++++++++
t/t5551-http-fetch.sh | 31 ++++++++++++++++++
6 files changed, 161 insertions(+), 3 deletions(-)
--
1.7.9.5.4.g4f508
next reply other threads:[~2012-04-02 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 15:11 Ivan Todoroski [this message]
2012-04-02 15:13 ` [PATCH v3 1/4] fetch-pack: new --stdin option to read refs from stdin Ivan Todoroski
2012-04-02 20:42 ` Jeff King
2012-04-02 15:14 ` [PATCH v3 2/4] remote-curl: send the refs to fetch-pack on stdin Ivan Todoroski
2012-04-02 18:50 ` Junio C Hamano
2012-04-02 15:16 ` [PATCH v3 3/4] fetch-pack: test cases for the new --stdin option Ivan Todoroski
2012-04-02 19:34 ` Junio C Hamano
2012-04-03 0:23 ` Ivan Todoroski
2012-04-02 15:17 ` [PATCH v3 4/4] remote-curl: main test case for the OS command line overflow Ivan Todoroski
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=4F79C195.6090905@gmx.net \
--to=grnch@gmx.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).