From: "Scott Chacon" <schacon@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Sky Patrick" <patricksky852@gmail.com>, git@vger.kernel.org
Subject: Re: Is there have development library or API for git ?
Date: Tue, 26 Aug 2008 11:48:53 -0700 [thread overview]
Message-ID: <d411cc4a0808261148g792c01ax325aff343e7c3333@mail.gmail.com> (raw)
In-Reply-To: <20080825041217.GA19127@spearce.org>
The Ruby library Grit actually does a lot of stuff in pure ruby rather
than forking, but you also might want to take a look at libgitcore:
http://git.codethink.co.uk/?p=git;a=shortlog;h=libgitcore
The codethink guys have stripped and rewritten a bunch of git to
behave more like a linkable library, and I think they have a python
binding as an example.
Scott
On Sun, Aug 24, 2008 at 9:12 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Sky Patrick <patricksky852@gmail.com> wrote:
>> Is there have development library or API for git ? Thank ~
>
> No. However you can look at jgit if you are programming in Java.
> In Ruby look up Grit (a wrapper around the plumbing commands), or
> the pure-Ruby implementation of Git (I forget its name).
>
> Anything else, use the plumbing commands and just fork+exec what
> you need. Many of them have a -z flag to use null termination
> on records, making it easier (and safer) to slurp data that may
> contain LFs.
>
> --
> Shawn.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2008-08-26 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <976e6d070808242025n24b282dei5c79b4c9bf2e390e@mail.gmail.com>
2008-08-25 4:09 ` Is there have development library or API for git ? Sky Patrick
2008-08-25 4:12 ` Shawn O. Pearce
2008-08-26 18:48 ` Scott Chacon [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=d411cc4a0808261148g792c01ax325aff343e7c3333@mail.gmail.com \
--to=schacon@gmail.com \
--cc=git@vger.kernel.org \
--cc=patricksky852@gmail.com \
--cc=spearce@spearce.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).