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

Re: GSoC questions

From
Vincent van Ravesteijn <vfr@lyx.org>
Date
Apr 1, 2011, 21:05 UTC
Message-ID
<4D963E09.10003@lyx.org>
In-Reply-To
<20110331192758.GD16981@sigill.intra.peff.net>
Show 6 quoted lines
>> I guess the git2 client will consist solely of non-gitcore code, as
>> all the gitcore code will be part of libgit2 eventually.
>>
> I had sort of assumed that git-core code would be taken as inspiration,
> but that it would be an entirely new implementation, based around the
> error handling and build infrastructure provided by libgit2.

Looking at the above, I think we completely agree. When I wrote that the gitcore code will get into libgit2, I indeed meant that it should be rewritten in the libgit2 style and then be added to libgit2.

There was also temporarily the idea for GSoC to let Git use the libgit2-library, or maybe to libify git on the road. That's why I thought it might be useful if we were not going to rewrite the boring administration code.

Thanks for thinking along,
Vincent
Previous: Jeff King
Message 12 of 12 in “GSoC questions”
  1. Alexandru SutiiMar 27, 2011
  2. Jonathan NiederMar 28, 2011
  3. Jeff KingMar 28, 2011
  4. Alexandru SutiiMar 28, 2011
  5. Vicent MartiMar 28, 2011
  6. Alexandru SutiiMar 31, 2011
  7. Motiejus JakštysMar 31, 2011
  8. Vincent van RavesteijnMar 31, 2011
  9. Alexandru SutiiMar 31, 2011
  10. Jeff KingMar 31, 2011
  11. Jeff KingMar 31, 2011
  12. Vincent van RavesteijnApr 1, 2011

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.