Git development
 help / color / mirror / Atom feed
From: Konstantin Khomoutov <kostix@bswap.ru>
To: Ana Jovanovska <ajovanovska@sumologic.com>
Cc: git@vger.kernel.org, Enrico Benzoni <ebenzoni@sumologic.com>,
	Michele Zambelli <mzambelli@sumologic.com>
Subject: Re: Git SCM API remote
Date: Wed, 15 Dec 2021 18:52:21 +0300	[thread overview]
Message-ID: <20211215155221.tzg55fxerpowj623@carbon> (raw)
In-Reply-To: <CA++hZeHEVN6JZMdtXMjG2bDqerJjrFjhjYOry_rnWDgjTbQ8aA@mail.gmail.com>

On Wed, Dec 15, 2021 at 01:57:42PM +0100, Ana Jovanovska wrote:

> I am developing the integration with Git SCM and I will need your help
> on this matter.
> This is API remote doc https://www.git-scm.com/docs/api-remote .
No, it is not.

Unfortunately, looks like your knowledge about Git itself is a bit lacking
currently as you appear to not be aware of Git's terminology.
I would say, reading a book on Git ([1] is good), and a couple of manuals on
it, possibly starting with [2].

> Can I have more information on how to use it, do I need some additional
> library?

Git itself does not ship anything you could call a library, but it is
comprised from a large number of individual commands (which are what you would
call "command-line commands") which are broadly divided into two categories -
for end users and for use by other commands; these groups are called
"porcelain" and "plumbing". Call out to plumbing-layer commands is the typical
way to automate Git.

If you need to somehow manipulate Git repositores - you did not say anything
about what that "integration" has to be about, - without having Git installed,
you may resort to 3rd-party libraries such as [3]. ISTR it also has wrapping
libraries in several programming languages.

Also note that there exist libraries for various programming languages which
wrap calls to plumbing-layer Git commands, so they sort of implement something
in between a "pure library" which does not call out to Git and calling Git
directly.

1. https://www.git-scm.com/book/en/v2
2. https://www.git-scm.com/docs/git
3. https://libgit2.org/


  reply	other threads:[~2021-12-15 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 12:57 Git SCM API remote Ana Jovanovska
2021-12-15 15:52 ` Konstantin Khomoutov [this message]
     [not found]   ` <CA++hZeFiFAuCD=C-2xJJt3yd5guyJrssjtpAmAqYXkMQuRtfpw@mail.gmail.com>
2022-01-03 14:51     ` Ana Jovanovska
2022-01-04 16:34       ` Konstantin Khomoutov

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=20211215155221.tzg55fxerpowj623@carbon \
    --to=kostix@bswap.ru \
    --cc=ajovanovska@sumologic.com \
    --cc=ebenzoni@sumologic.com \
    --cc=git@vger.kernel.org \
    --cc=mzambelli@sumologic.com \
    /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