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

git-p4 using notes

From
MHMichael Horowitz <michael.horowitz@ieee.org>
Date
Dec 16, 2011, 16:07 UTC
Message-ID
<CAFLRbori1Dinc2epputWfjgCOWp7M2f=+TA0w2jHq_fmRC=y3w@mail.gmail.com>

For those of you using git-p4 because of a company requirement to use Perforce, but really wish you could use git only, the most frustrating part is the fact that when changes are submitted, the commit message is rewritten to include a reference to the P4 change number which is used by the sync. When syncing back changes, this causes the commit hash to be different, and so blows away your old commit and any parent commit references and such.

I read someplace, I can't remember where at this point, that if git-p4 used notes to write the P4 change information, that would not impact the commit hash, so when merging back, things would not be overwritten, and you can maintain branches and commit history properly in git.

I just ran into this project, where it seems that someone has re-written git-p4 to use notes: https://github.com/ermshiperete/git-p4

I was wondering if any of the maintainers of git-p4 has considered this, and might want to leverage this work to merge into the main git repo, possibly with an option to choose between the two behaviors.

Thanks,
Mike
Next: Luke Diamand
Message 1 of 3 in “git-p4 using notes”
  1. Michael HorowitzDec 16, 2011
  2. Luke DiamandDec 16, 2011
  3. Michael HorowitzDec 17, 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.