Re: About GIT Internals
- From
- Aman <amanmatreja@gmail.com>
- Date
- Jun 4, 2022, 15:24 UTC
- Message-ID
- <CACMKQb3gYwdyfRSLWO4FWb6+Kxrk-WURpLayrgFsszCKMhWONw@mail.gmail.com>
- 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.
Show 5 quoted lines
> 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?