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

[PATCH 0/2] git p4: use "move" command for renames

From
PWPete Wyckoff <pw@padd.com>
Date
Jul 4, 2012, 13:40 UTC
Message-ID
<1341409220-27954-1-git-send-email-pw@padd.com>

Recent p4 supports a "move" command that records explicitly that a file was moved from one place to another. It can be changed a bit during the move, too. Use this feature, if it exists, when renames are detected.

Gary sent these patches months ago, and I've been sitting on them far too long. Was hoping to move some other work out first, but it was not ready.

These commits are on origin/next, as they depend on changes in pw/git-p4-tests that was merged into next on Jul 3. They do not conflict with the other series in flight, "notice Jobs: ...".

Gary Gibbons (2):
  git p4: refactor diffOpts calculation
  git p4: add support for 'p4 move' in P4Submit
 Documentation/git-p4.txt | 10 +++---
 git-p4.py                | 86 ++++++++++++++++++++++++++++++++----------------
 t/t9814-git-p4-rename.sh | 16 ++++-----
 3 files changed, 72 insertions(+), 40 deletions(-)
-- 
1.7.11.1.125.g4a65fea
Next: Pete Wyckoff
Message 1 of 5 in “git p4: use "move" command for renames”
  1. 0/2 git p4: use "move" command for renamesPete Wyckoff, Jul 4, 2012
  2. 1/2 git p4: refactor diffOpts calculationPete Wyckoff, Jul 4, 2012
  3. 2/2 git p4: add support for 'p4 move' in P4SubmitPete Wyckoff, Jul 4, 2012
  4. Junio C HamanoJul 6, 2012
  5. Pete WyckoffJul 9, 2012

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.