From: git-vger@eldondev.com
To: Aman <amanmatreja@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: About GIT Internals
Date: Wed, 25 May 2022 23:34:18 +0000 [thread overview]
Message-ID: <Yo68+kjAeP6tnduW@invalid> (raw)
In-Reply-To: <CACMKQb0Mz4zBoSX2CdXkeF51z_mh3had7359J=LmXGzJM1WYLg@mail.gmail.com>
Hi Aman, responses inline below.
On Wed, May 25, 2022 at 09:40:42PM +0530, Aman wrote:
> Could someone please assist - in sharing some resources - which I
> could go through, to better understand GIT software internals.
There is an excellent free book at https://git-scm.com/book/en/v2 .
Chapter 10 is about git internals. It is important to realize that,
unlike many other version control systems, git works effectively on
files locally on your computer, without any server or other shared
resources to manage. Also, one good way to learn may be to form a
question that you want to answer first. "How do I ...." or "what happens
when I ....". Since git works locally, it is possible to create a git
repo, look at the files contained in the .git directory, take action
with git, and then look at the files again.
Many people use git from the command line. If you are not familiar with
the command line, you may be interesting in learning more about it.
Mozilla, the makers of the Firefox web browser, have a wiki page to
familiarize yourself with the command line here:
https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Command_line
Happy Explorations!
Eldon
next prev parent reply other threads:[~2022-05-25 23:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 16:10 About GIT Internals Aman
2022-05-25 16:49 ` Emily Shaffer
2022-05-25 21:14 ` Erik Cervin Edin
2022-05-25 23:34 ` git-vger [this message]
2022-05-26 8:47 ` Philip Oakley
[not found] ` <CACMKQb3exv13sYN5uEP_AG-JYu1rmVj4HDxjdw8_Y-+maJPwGg@mail.gmail.com>
2022-05-27 14:40 ` Philip Oakley
[not found] ` <C4B1A93D-800F-4C49-93D5-86FE58B1DDCA@hxcore.ol>
2022-05-27 15:14 ` Philip Oakley
2022-05-30 9:49 ` Kerry, Richard
2022-05-30 11:53 ` Konstantin Khomoutov
2022-05-30 13:50 ` Ævar Arnfjörð Bjarmason
2022-06-03 12:18 ` Aman
2022-06-03 15:23 ` Konstantin Khomoutov
2022-06-04 15:24 ` Aman
2022-06-06 11:52 ` Konstantin Khomoutov
2022-06-03 15:25 ` Emily Shaffer
2022-06-03 17:15 ` Junio C Hamano
2022-05-26 12:45 ` 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=Yo68+kjAeP6tnduW@invalid \
--to=git-vger@eldondev.com \
--cc=amanmatreja@gmail.com \
--cc=git@vger.kernel.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).