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

Re: Using trees for metatagging

From
Avery Pennarun <apenwarr@gmail.com>
Date
Feb 18, 2010, 23:32 UTC
Message-ID
<32541b131002181532h79d3250fid5984f46f82b71f9@mail.gmail.com>
In-Reply-To
<20100218232523.GD22371@lapse.rw.madduck.net>
On Thu, Feb 18, 2010 at 6:25 PM, martin f krafft <madduck@madduck.net> wrote:
Show 6 quoted lines
> also sprach Avery Pennarun <apenwarr@gmail.com> [2010.02.19.1206 +1300]:
>> So checking in a file that contains a list of object ids (or
>> filenames) is perfectly appropriate.
>
> Indeed. But Git provides a lot of tools to manipulate all those,
> which I would not be able to reuse in the text-file approach.

But you're talking about using a nonstandard approach anyway (unless you use git-notes). So you'd end up rolling your own code with git's plumbing anyway, which you can do just as easily with a text file full of object ids.

Once you have an object id, there are plenty of existing git commands to do whatever you want.

Have fun,
Avery
Previous: martin f krafftNext: Johan Herland
Message 8 of 9 in “Using trees for metatagging”
  1. martin f krafftFeb 18, 2010
  2. Avery PennarunFeb 18, 2010
  3. martin f krafftFeb 18, 2010
  4. Johan HerlandFeb 18, 2010
  5. martin f krafftFeb 18, 2010
  6. Avery PennarunFeb 18, 2010
  7. martin f krafftFeb 18, 2010
  8. Avery PennarunFeb 18, 2010
  9. Johan HerlandFeb 19, 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.