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

Re: [PATCH] graph.c: make many functions static

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 20, 2008, 07:37 UTC
Message-ID
<7vmylgo8v7.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080620060035.GA22345@adamsimpkins.net>
Adam Simpkins <adam@adamsimpkins.net> writes:
Show 17 quoted lines
> On Thu, Jun 19, 2008 at 12:16:11PM -0700, Junio C Hamano wrote:
>> しらいしななこ  <nanako3@lavabit.com> writes:
> ...
>> > +/* Internal API */
>> > + ...
>> > +static int graph_next_line(struct git_graph *graph, struct strbuf *sb);
>> > +static void graph_padding_line(struct git_graph *graph, struct strbuf *sb);
>> > +static void graph_show_strbuf(struct git_graph *graph, struct strbuf const *sb);
>> 
>> I think these are probably fine, not in the sense that nobody calls these
>> functions _right now_ but in the sense that I do not foresee a calling
>> sequence outside the graph.c internal that needs to call these directly,
>> instead of calling graph_show_*() functions that use these.
>
> Documentation/technical/api-history-graph.txt should also be updated
> to remove the discussion of these functions if they are no longer
> publicly exposed.

Actually, I was expecting (not necessarily _hoping_) you to defend these public API by providing examples that illustrates when calling these from outside graph API implementation could be useful.

Previous: Adam SimpkinsNext: Adam Simpkins
Message 4 of 5 in “graph.c: make many functions static”
  1. graph.c: make many functions staticしらいしななこ, Jun 18, 2008
  2. Junio C HamanoJun 19, 2008
  3. Adam SimpkinsJun 20, 2008
  4. Junio C HamanoJun 20, 2008
  5. Adam SimpkinsJun 20, 2008

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.