From: Luke Diamand <luke@diamand.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Lex Spoon <lex@lexspoon.org>,
Luke Diamand <luke@diamand.org>
Subject: [PATCHv2 0/3] git-p4: fixing --changes-block-size handling
Date: Sun, 7 Jun 2015 22:35:02 +0100 [thread overview]
Message-ID: <1433712905-7508-1-git-send-email-luke@diamand.org> (raw)
In-Reply-To: <55747A05.3070704@diamand.org>
Updated per Lex's suggestion, so that git-p4 always uses the block mode,
and takes advantage of this to simplify the loop. This exposed a bug
in the termination condition.
One thing to note: 'git p4 sync' claims to support arbitrary p4 revision
specifications. I need to check that this is tested and hasn't been broken
by these changes.
Luke
Luke Diamand (3):
git-p4: additional testing of --changes-block-size
git-p4: test with limited p4 server results
git-p4: fixing --changes-block-size handling
git-p4.py | 45 ++++++++++++++++++------------
t/t9818-git-p4-block.sh | 73 +++++++++++++++++++++++++++++++++++++++++++------
2 files changed, 92 insertions(+), 26 deletions(-)
--
2.4.1.502.gb11c5ab
next prev parent reply other threads:[~2015-06-07 21:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 10:21 [PATCHv1 0/3] git-p4: fixing --changes-block-size support Luke Diamand
2015-06-07 10:21 ` [PATCHv1 1/3] git-p4: additional testing of --changes-block-size Luke Diamand
2015-06-07 16:06 ` Lex Spoon
2015-06-07 10:21 ` [PATCHv1 2/3] git-p4: test with limited p4 server results Luke Diamand
2015-06-07 16:11 ` Lex Spoon
2015-06-07 10:21 ` [PATCHv1 3/3] git-p4: fixing --changes-block-size handling Luke Diamand
2015-06-07 16:33 ` Lex Spoon
2015-06-07 17:06 ` Luke Diamand
2015-06-07 21:35 ` Luke Diamand [this message]
2015-06-07 21:35 ` [PATCHv2 1/3] git-p4: additional testing of --changes-block-size Luke Diamand
2015-06-07 21:35 ` [PATCHv2 2/3] git-p4: test with limited p4 server results Luke Diamand
2015-06-07 21:35 ` [PATCHv2 3/3] git-p4: fixing --changes-block-size handling Luke Diamand
2015-06-07 22:58 ` Lex Spoon
2015-06-08 16:02 ` Junio C Hamano
2015-06-08 16:36 ` Lex Spoon
[not found] ` <xmqqy4juazkz.fsf@gitster.dls.corp.google.com>
[not found] ` <5575E264.6040601@diamand.org>
2015-06-08 22:32 ` Junio C Hamano
2015-06-07 16:01 ` [PATCHv1 0/3] git-p4: fixing --changes-block-size support Lex Spoon
2015-06-07 16:58 ` Luke Diamand
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=1433712905-7508-1-git-send-email-luke@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lex@lexspoon.org \
/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).