git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Nomad Arton <lkml@lazy.shacknet.nu>
Cc: git@vger.kernel.org
Subject: Re: using git directory cache code in darcs?
Date: Sun, 17 Apr 2005 16:23:36 -0700	[thread overview]
Message-ID: <7vvf6lugw7.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <4262E50C.2070006@lazy.shacknet.nu> (Nomad Arton's message of "Mon, 18 Apr 2005 00:37:00 +0200")

>>>>> "NA" == Nomad Arton <lkml@lazy.shacknet.nu> writes:

NA> Linus Torvalds schrieb:
>> In fact, one of my hopes was that other SCM's could just use the git
>> plumbing. But then I'd really suggest that you use "git" itself, not any
>> "libgit". Ie you take _all_ the plumbing as real programs, and instead of
>> trying to link against individual routines, you'd _script_ it.

NA> please excuse; libgit and scripting to me arent a contradiction. many
NA> sripting languages are extended by C modules, while still happening to
NA> have all the scripting rapidity. its just a matter of how to
NA> communicate with the C code, isnt it?

You are arguing for scripting language binding like what Swig
creates.  While that would also be a worthy addition, having
language binding is not the only way to do _script_.

What Linus is saying is that he wants you to talk with git
plumbing by invoking the executables he have, via system(3),
popen(3), etc.

The C-level first has to be libified before you can start
talking about host language bindings but that just started to
happen and is not ready yet.  However, you can use and benefit
from GIT without waiting for that kind of integration, if you
use the "spawning the executables" approach.  I agree with him.


  reply	other threads:[~2005-04-17 23:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16 13:22 using git directory cache code in darcs? David Roundy
2005-04-16 13:31 ` Ingo Molnar
2005-04-16 14:28 ` Junio C Hamano
2005-04-16 22:43 ` Linus Torvalds
2005-04-17 12:17   ` David Roundy
2005-04-17 16:24     ` Linus Torvalds
2005-04-17 16:49       ` Mike Taht
2005-04-17 22:37       ` Nomad Arton
2005-04-17 23:23         ` Junio C Hamano [this message]
2005-04-18  2:00           ` Paul Jackson
2005-04-18  2:56       ` Paul Jackson
2005-04-18  3:06         ` Linus Torvalds
2005-04-18  4:36           ` Paul Jackson
2005-04-18  9:23             ` git options Mike Taht

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=7vvf6lugw7.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=lkml@lazy.shacknet.nu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).