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

Re: [PATCH] technical-docs: document tree-walking API

From
Stephen Boyd <bebarino@gmail.com>
Date
Aug 4, 2009, 06:00 UTC
Message-ID
<4A77CE9B.2060102@gmail.com>
In-Reply-To
<7v4oso87fy.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
Show 5 quoted lines
> I think the primary author is Linus for this API, but once you finished
> the documentation, I do not think "authors" section is particularly
> needed (git knows who the code came from reasonably well anyway).  The
> names of people in these stub documents were there for people like you;
> see 530e741 (Start preparing the API documents., 2007-11-24).
I'm ok with dropping the Authors section then.
Show 7 quoted lines
>
> It might be a bit misleading to say that the path member of struct
> name_entry is a "pathname".  It is _one_ path component, and by stringing
> multiple struct traverse_info's (each of which has one struct name_entry)
> together with their prev pointer, make_traverse_path() can reconstruct the
> full pathname from the toplevel down to the level you have traversed into.
> We may want to say "path component" to clarify the distinction.

This sounds reasonable for the traversing section. I'm a bit confused about how it would work for the walking section though. I don't get the notion of path components there because the API is focused around one level of a tree. Maybe it should just be called the entry's name in that case?

Previous: Junio C Hamano
Message 3 of 3 in “technical-docs: document tree-walking API”
  1. technical-docs: document tree-walking APIStephen Boyd, Aug 4, 2009
  2. Junio C HamanoAug 4, 2009
  3. Stephen BoydAug 4, 2009

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.