git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: Walking commits from the first
Date: Mon, 15 Feb 2010 10:09:02 +0530	[thread overview]
Message-ID: <e72faaa81002142039h5531a19y354d24e595295bb1@mail.gmail.com> (raw)
In-Reply-To: <e72faaa81002142037g7f5f518erb9fefbb239124bc5@mail.gmail.com>

Hi,

 When you clone a big git repository and would like to read and
understand the source code, you need to checkout and read every commit
right from the first commit. As per my knowledge, there is no command
(even with flags) to checkout the first commit of the repository.

If there is some command, please put it in user's manual

Also if we somehow managed to do it by a series of commands, after we
finish reading it then we need to redo it all over again to checkout
the next commit.

So, what i would like to have is something like this:
1) git checkout --first
   Checksout the commit #1 of the git repository
2) git checkout --next
   Checksout the next commit

What I think:

I know that every git commit is a vertice in a DAG which has it's edge
pointed to it's parent. So, walking from the latest commits to old
commits is easy but the reverse is not.
I would like to know if there is any problem if we make the walking
bidirectional. What i mean is, when a new commit is created, create an
edge not only from it to it's parent but also from it's parent to it.
Also, have something for the first commit of the repo which can be
referred as INIT (similiar to HEAD)

-pavan

       reply	other threads:[~2010-02-15  4:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e72faaa81002142037g7f5f518erb9fefbb239124bc5@mail.gmail.com>
2010-02-15  4:39 ` Pavan Kumar Sunkara [this message]
2010-02-15  8:06   ` Walking commits from the first Jeff King
2010-02-15 11:33     ` Pavan Kumar Sunkara
2010-02-15 14:05       ` Jon Seymour
2010-02-15 14:20         ` Jon Seymour

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=e72faaa81002142039h5531a19y354d24e595295bb1@mail.gmail.com \
    --to=pavan.sss1991@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).