Re: About GIT Internals

From: Aman <amanmatreja@gmail.com>
To: Konstantin Khomoutov <kostix@bswap.ru>
Cc: "Git List" <git@vger.kernel.org>,
	"Kerry, Richard" <richard.kerry@atos.net>,
	"Philip Oakley" <philipoakley@iee.email>,
	"git-vger@eldondev.com" <git-vger@eldondev.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: About GIT Internals
Date: Sat, 4 Jun 2022 20:54:10 +0530	[thread overview]
Message-ID: <CACMKQb3gYwdyfRSLWO4FWb6+Kxrk-WURpLayrgFsszCKMhWONw@mail.gmail.com> (raw)
In-Reply-To: <20220603152301.olqbjtt5j2kqyc3e@carbon>

On Fri, Jun 3, 2022, at 8:53 PM Konstantin Khomoutov <kostix@bswap.ru> wrote:

> Well, depends on what you mean when talking about the two mentioned designs.
> I mean, there's the design of the approach to manage data and there's the
> design of the software package (which Git is).

That's a good perspective on the distinction between the designs. I am
not familiar yet, with the design of GIT as a software package, and I
am guessing most people who'll be learning about GIT internals won't
be.

> If you do also understand the latter - that is, understanding that Git is an
> assortment of CLI tools combined into two layers called "plumbing" and
> "porcelain", - then you should have no difficulty starting to read the code:
> basically locate the source code of the entry point Git binary (which is,
> well, "git", or "git.exe" on Windows) and start reading it.

How do I do that?  What do you mean by the "entry point" of the git binary?