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

Storing notes refs outside of refs/

From
Joshua Jensen <jjensen@workspacewhiz.com>
Date
Aug 26, 2010, 15:02 UTC
Message-ID
<4C7681F1.3070205@workspacewhiz.com>
  Every push to our server creates a note at .git/refs/notes/p4notes 
with the equivalent Perforce changelist number, so Git-controlled code 
and Perforce-controlled content can stay in sync.

gitk --all and Git Extensions (out of box) show all entries in the .git/refs/. The p4notes entries are intermixed with the regular branch content. This creates a HORRID visual mess.

I tried manually moving .git/refs/notes/p4notes to .git/p4/p4notes.

"git log --show-notes=p4/p4notes" fails, but assigning core.notesDisplayRef=p4/p4notes succeeds.

The best part is, the refs/* namespace is no longer cluttered with junk!

However, "git push origin p4/p4notes:p4/p4notes" fails with the error: Unable to push to unqualified destination: p4/p4notes. The destination refspec neither matches an existing ref on the remote nor begins with refs/, and we are unable to guess a prefix based on the source ref.

Is there a way to make the "git push" work?
Thanks!
Josh
Next: Junio C Hamano
Message 1 of 8 in “Storing notes refs outside of refs/”
  1. Joshua JensenAug 26, 2010
  2. Junio C HamanoAug 26, 2010
  3. Joshua JensenAug 26, 2010
  4. Junio C HamanoAug 26, 2010
  5. Joshua JensenAug 26, 2010
  6. Tomas CarneckyAug 26, 2010
  7. Sverre RabbelierAug 26, 2010
  8. Tomas CarneckyAug 26, 2010

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.