Re: Question: regarding understanding code base

From: Ben Knoble <ben.knoble@gmail.com>
Date: Jun 15, 2025, 00:26 UTC
Message-ID: <AF617F39-7B22-44A3-BF08-D21CCFBEBD20@gmail.com>
In-Reply-To: <CA+rGoLf8Lf0gbPEUjTU9Zc9KQrzui4pjyvfxhA-LT4YuafqeOQ@mail.gmail.com>

Show 11 quoted lines

> Le 14 juin 2025 à 08:44, JAYATHEERTH K <jayatheerthkulkarni2005@gmail.com> a écrit :
> 
> Ok so a couple of weeks ago, in this thread[1]
> Junio advised that one of the best ways to understand git is to go back to the
> _inital commit_ and travel back to the latest ones.
> 
> And I happened to quite like this idea, cause I still have to dig up a
> lot of things in git.
> The main question is
> What are the best and smallest set of git commands to do this as
> I can set this up as an alias and use this trick for many other projects too.

If you want a checkout of the root commit, assuming there’s only one, something like

    git rev-list | sed -n \$p | xargs git switch --detach

ought to work. You could feed something similar to git-worktree. But it’s a little harder to “go forward” with Git’s data model, and I didn’t totally understand “travel back to the latest ones.”

Show 8 quoted lines

> 
> 1 - https://lore.kernel.org/git/xmqqfrh3qe2w.fsf@gitster.g/
> 
> 
> Thank you,
> 
> - Jayatheerth
>