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

Re: [RFC] [GSoC] Draft of Proposal for GSoC

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 21, 2014, 17:45 UTC
Message-ID
<xmqq8us3v42o.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAM+=D-ATimdXmcYpqSyKwZXE=TYXg9cZFG9kyjEOg22K1wF+3Q@mail.gmail.com>
Brian Bourn <ba.bourn@gmail.com> writes:
Show 11 quoted lines
> Something like this?
>
> Sample api calls
> Add_Opt_Group()
> Parse_with_contains()
> Parse_with_merged()
> Parse_with_no_merged()
> Parse_with_formatting()
> (each of the 4 calls above may have internal calls within the library
> in order to parse the option for each of the different function which
> may call these functions)

This list is a bit too sketchy to be called "sample api calls", at least to me. Can you elaborate a bit more?

What do they do, what does the caller expect to see (do they get something as return values? do they expect some side effects?)?

Previous: Brian BournNext: Brian Bourn
Message 5 of 8 in “[RFC] [GSoC] Draft of Proposal for GSoC”
  1. Brian BournMar 20, 2014
  2. Brian BournMar 21, 2014
  3. Jeff KingMar 21, 2014
  4. Brian BournMar 21, 2014
  5. Junio C HamanoMar 21, 2014
  6. Brian BournMar 21, 2014
  7. Jeff KingMar 21, 2014
  8. Brian BournMar 21, 2014

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.