git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Larsen <bryan.larsen@gmail.com>
To: Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>
Cc: darcs-devel@darcs.net, git@vger.kernel.org
Subject: Re: git, porcelain, darcs, and version 1.0
Date: Mon, 18 Jul 2005 16:28:26 -0400	[thread overview]
Message-ID: <42DC10EA.4050502@gmail.com> (raw)
In-Reply-To: <7id5pfx5ci.fsf@lanthane.pps.jussieu.fr>


>>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

      reply	other threads:[~2005-07-18 20:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-16 20:45 Darcs-Git: upgrading to Git 0.99 Juliusz Chroboczek
2005-07-17 10:40 ` [darcs-devel] " David Roundy
2005-07-18  4:46 ` git, porcelain, darcs, and version 1.0 Bryan Larsen
2005-07-18 19:11   ` Junio C Hamano
2005-07-18 20:18     ` Bryan Larsen
2005-07-18 19:49   ` Juliusz Chroboczek
2005-07-18 20:28     ` Bryan Larsen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42DC10EA.4050502@gmail.com \
    --to=bryan.larsen@gmail.com \
    --cc=Juliusz.Chroboczek@pps.jussieu.fr \
    --cc=darcs-devel@darcs.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).