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

Porcelain specific metadata under .git?

From
Shawn Pearce <spearce@spearce.org>
Date
Jun 14, 2006, 06:22 UTC
Message-ID
<20060614062240.GA13886@spearce.org>

So I'm reaching a point with my Eclipse plugin[*1*] where its actually doing something with a GIT repository and I want to store a ref (to a tree, not a commit) under .git/refs/eclipse-workspaces to help the plugin cache state between workbench restarts. But there doesn't really seem to be any policy to what paths under .git are available for Porcelain and what definately should be off-limits.

I already assume/know that refs/heads and refs/tags are completely off-limits as they are for user refs only.

I also think the core GIT tools already assume that anything directly under .git which is strictly a file and which is named entirely with uppercase letters (aside from "HEAD") is strictly a temporary/short-lived state type item (e.g. COMMIT_MSG) used by a Porcelain.

But is saying ".git/refs/eclipse-workspaces" is probably able to be used for this purpose safe? :-)

[*1*] The Eclipse plugin is getting close to something that is worth releasing as an early alpha for other developers. I think I finally found the last bug in the pack reading code and am now working on the basic operations (add/remove/commit/status). I hope to have all of that working within a few days, at which point I'll publish/announce a public GIT repository with the complete source code and an Eclipse update site for those brave souls who might want to just install it.

-- 
Shawn.
Next: Andreas Ericsson
Message 1 of 6 in “Porcelain specific metadata under .git?”
  1. Shawn PearceJun 14, 2006
  2. Andreas EricssonJun 14, 2006
  3. Jakub NarebskiJun 14, 2006
  4. Andreas EricssonJun 14, 2006
  5. Junio C HamanoJun 14, 2006
  6. Shawn PearceJun 17, 2006

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.