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

Re: [PATCh] jit-trackdown

From
Junio C Hamano <junkio@cox.net>
Date
Apr 29, 2005, 22:09 UTC
Message-ID
<7vr7gt2q29.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.21.0504291730000.30848-100000@iabervon.org>
>>>>> "DB" == Daniel Barkalow <barkalow@iabervon.org> writes:
DB> I've made a proposal like the following:

DB> .git/ DB> objects/ (traditional) DB> refs/ Directories of hex SHA1 + newline files DB> heads/ Commits which are heads of various sorts DB> tags/ Tags, by the tag name (or some local renaming of it) DB> info/ Other shared information DB> remotes DB> ... Everything else isn't shared DB> HEAD Symlink to refs/heads/<something>

Thank you for clear description.

I agree with Linus that plumbing does not need to know anything but objects/. What the porcelain passes fsck-cache to implement prune/garbage-collect does not concern it. Of course it matters to the users and that is the reason why I asked.

Previous: Daniel Barkalow
Message 4 of 4 in “jit-trackdown”
  1. jit-trackdownDavid Greaves, Apr 29, 2005
  2. Junio C HamanoApr 29, 2005
  3. Daniel BarkalowApr 29, 2005
  4. Junio C HamanoApr 29, 2005

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.