git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCHv2 0/3] git-p4: fixing --changes-block-size handling

From
Luke Diamand <luke@diamand.org>
Date
Jun 7, 2015, 21:35 UTC
Message-ID
<1433712905-7508-1-git-send-email-luke@diamand.org>
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
Previous: Luke DiamandNext: Luke Diamand
Message 9 of 18 in “[PATCHv1 0/3] git-p4: fixing --changes-block-size support”
  1. Luke DiamandJun 7, 2015
  2. 1/3 git-p4: additional testing of --changes-block-sizeLuke Diamand, Jun 7, 2015
  3. Lex SpoonJun 7, 2015
  4. 2/3 git-p4: test with limited p4 server resultsLuke Diamand, Jun 7, 2015
  5. Lex SpoonJun 7, 2015
  6. 3/3 git-p4: fixing --changes-block-size handlingLuke Diamand, Jun 7, 2015
  7. Lex SpoonJun 7, 2015
  8. Luke DiamandJun 7, 2015
  9. 0/3 git-p4: fixing --changes-block-size handlingLuke Diamand, Jun 7, 2015
  10. 1/3 git-p4: additional testing of --changes-block-sizeLuke Diamand, Jun 7, 2015
  11. 2/3 git-p4: test with limited p4 server resultsLuke Diamand, Jun 7, 2015
  12. 3/3 git-p4: fixing --changes-block-size handlingLuke Diamand, Jun 7, 2015
  13. Lex SpoonJun 7, 2015
  14. Junio C HamanoJun 8, 2015
  15. Lex SpoonJun 8, 2015
  16. Lex SpoonJun 7, 2015
  17. Luke DiamandJun 7, 2015
  18. Junio C HamanoJun 8, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.