Re: Regarding GIT API

From: Michael J Gruber <git@drmicha.warpmail.net>
Date: Feb 15, 2011, 12:40 UTC
Message-ID: <4D5A744F.5000208@drmicha.warpmail.net>
In-Reply-To: <AANLkTim4ucYtoyNEM2+=-dJTmpBtqy1zJOEX3k3Wk+XU@mail.gmail.com>

Dmitry Potapov venit, vidit, dixit 15.02.2011 12:49:

Show 11 quoted lines

> On Tue, Feb 15, 2011 at 11:08:14AM +0000, Abhinav Goyal wrote:
>> I just need the git command
>> support for my C++ application. I have my own reason for not using command
>> prompt system call.
> 
> If you need full git functionality, currently the only proper way is to
> use git porcelain command, i.e. run commands using system() and parse
> their output. Git porcelain commands are designed to be used in this way,
> so their output is easy to parse. Also, their output should not change
> between different versions, in contrast to front-end git commands, which
> provide more human oriented output.

You mean "plumbing" for the commands with robust interface.

The front-end commands are "porcelain": they may break when used for heavy (scripting) work...

Show 13 quoted lines

> 
> NOTE: There are libraries for some other languages such as Java and Ruby
> (jGit and Grit correspondingly), but they contain re-implementation of
> most git functionality. No one has bothered to write anything like that
> in C. So, libgit2 provides only low-level and very limited functionality.
> 
> More information about git interfaces to different languages, you can
> find here:
> 
> https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#Interfaces_to_other_programming_languages
> 
> 
> Dmitry