From: Junio C Hamano <gitster@pobox.com>
To: JAYATHEERTH K <jayatheerthkulkarni2005@gmail.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: Question: regarding understanding code base
Date: Sat, 14 Jun 2025 17:43:26 -0700 [thread overview]
Message-ID: <xmqqldpt6dht.fsf@gitster.g> (raw)
In-Reply-To: <CA+rGoLehMUWPMBrZ1hOk-GBQBCvSY0_ivFCn1w1C-V_bGTDgZg@mail.gmail.com> (JAYATHEERTH K.'s message of "Sun, 15 Jun 2025 05:54:46 +0530")
JAYATHEERTH K <jayatheerthkulkarni2005@gmail.com> writes:
> What I meant was:
> You previously suggested that one good way to understand Git is to
> start from the initial commit of the Git repo and move forward
> chronologically through the commits.
Not at all. I only suggested to study the initial one. It is more
like biology students learning the common principles that apply to
all kinds of life by studying a lot simpler organism as a model,
instead of studying a lot higher order ones like mammals.
Moving forward is all your invention or hallucination ;-)
> - Start from the initial commit of a repository
>
> - Walk forward through history (one commit at a time) probably which
> changes my file system (I currently use a terminal based command)
>
> I use
> git rev-list --reverse HEAD | while read commit; do
> echo "=== Commit: $commit ==="
> git show --color --stat --patch --pretty=fuller "$commit"
> read -p "Press enter to continue to the next commit..."
> done
>
> I wanted to know if there are any better ways
Like "git log --reverse -p"?
next prev parent reply other threads:[~2025-06-15 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 12:43 Question: regarding understanding code base JAYATHEERTH K
2025-06-14 15:43 ` Junio C Hamano
2025-06-15 0:24 ` JAYATHEERTH K
2025-06-15 0:43 ` Junio C Hamano [this message]
2025-06-15 0:48 ` JAYATHEERTH K
2025-06-16 0:40 ` Junio C Hamano
2025-06-16 9:44 ` JAYATHEERTH K
2025-06-15 0:26 ` Ben Knoble
2025-06-15 0:37 ` JAYATHEERTH K
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=xmqqldpt6dht.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jayatheerthkulkarni2005@gmail.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