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

git-p4: problem with commit 97a21ca50ef8

From
Michael Wookey <michaelwookey@gmail.com>
Date
Oct 31, 2011, 23:11 UTC
Message-ID
<CAOk9v+-==GwDQaZ=4BW1QfEF7+5SfhNF409Xom0bHdT_qKaiFA@mail.gmail.com>
[ please CC me as I am not subscribed to the list ]
Hi,

Commit 97a21ca50ef893a171a50c863fe21a924935fd2a "git-p4: stop ignoring apple filetype" isn't correct. Without knowing too much about how git-p4 works, it appears that the "apple" filetype includes the resource fork, and the "p4 print" that is used to obtain the content from the perforce server doesn't take this into account, or maybe some post processing of the file needs to be done to include the data, but not the resource fork, before inclusion into the git repo.

With the above commit, a binary blob that literally contains the resource fork and data is included within the git repo. Of course, without the above commit, the intended file was never included in the git repo at all. Perhaps the resource fork issue was a known problem by the original git-p4 author.

A sample file that that demonstrates what the above commit produces is here (use curl/wget):

  http://dl.dropbox.com/u/1006983/sample_image_fail.png

This is literally a binary blob with about 110 KiB of resource fork plus the PNG data. The same image, minus about 110 KiB of resource fork is here:

  http://dl.dropbox.com/u/1006983/sample_image_correct.png

I'm happy to test patches as we have a perforce repository with files of the "apple" filetype.

Thanks
Next: Pete Wyckoff
Message 1 of 10 in “git-p4: problem with commit 97a21ca50ef8”
  1. Michael WookeyOct 31, 2011
  2. Pete WyckoffNov 1, 2011
  3. Michael WookeyNov 1, 2011
  4. Vitor AntunesNov 2, 2011
  5. Michael WookeyNov 2, 2011
  6. Vitor AntunesNov 3, 2011
  7. Pete WyckoffNov 4, 2011
  8. git-p4: ignore apple filetypePete Wyckoff, Nov 5, 2011
  9. Michael WookeyNov 7, 2011
  10. Junio C HamanoNov 7, 2011

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.