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

Re: git, porcelain, darcs, and version 1.0

From
Bryan Larsen <bryan.larsen@gmail.com>
Date
Jul 18, 2005, 20:28 UTC
Message-ID
<42DC10EA.4050502@gmail.com>
In-Reply-To
<7id5pfx5ci.fsf@lanthane.pps.jussieu.fr>
Show 9 quoted lines
>>Darcs and git work together to determine the minimal amount
>>that needs to go into libgit1.so.
> 
> 
> Hold on...  Nobody is speaking about *binary* compatibility, it's
> source-level compatibility that we need.  There is absolutely no
> reason to introduce the complexities of shared libraries into the
> picture.
>

Source level compatibility and stability is the big deal. Compared to that, shared libraries are an implementation detail, in my opinion. Sometimes those details get "interesting", but they are soluble.

I could care less whether you use libgit.a or a libgit.so. Just as long as distros or anybody else can update their darcs if a major data-loss bug is found in git. A recompile is acceptable. Dealing with the addition of a parameter to index_fd() is not.

Bryan
Previous: Juliusz Chroboczek
Message 7 of 7 in “Darcs-Git: upgrading to Git 0.99”
  1. Juliusz ChroboczekJul 16, 2005
  2. David RoundyJul 17, 2005
  3. git, porcelain, darcs, and version 1.0Bryan Larsen, Jul 18, 2005
  4. Junio C HamanoJul 18, 2005
  5. Bryan LarsenJul 18, 2005
  6. Juliusz ChroboczekJul 18, 2005
  7. Bryan LarsenJul 18, 2005

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.