From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: hong zhang <henryzhang62@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: how the commit ID come from in GIT?
Date: Tue, 6 Nov 2012 03:04:32 +0400 [thread overview]
Message-ID: <20121105230430.GK5210@localhost.localdomain> (raw)
In-Reply-To: <1352145846.26267.YahooMailClassic@web141404.mail.bf1.yahoo.com>
On Mon, Nov 05, 2012 at 12:04:06PM -0800, hong zhang wrote:
> Could anyone explain how the git commit ID will include all the files
> that devloper makes changes on?
>
> How git commit ID works?
To expand on the answer provided by Magnus, I would also suggest reading
the classic "Git from the bottom up" document [1], and if you want a
totally informal and fun introduction to how these cryptographic hashes
come about and why they are useful, I suggest reading
"The Git Parable" [2].
1. http://newartisans.com/2008/04/git-from-the-bottom-up/
2. http://tom.preston-werner.com/2009/05/19/the-git-parable.html
prev parent reply other threads:[~2012-11-05 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 20:04 how the commit ID come from in GIT? hong zhang
2012-11-05 20:26 ` Magnus Bäck
2012-11-05 23:04 ` Konstantin Khomoutov [this message]
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=20121105230430.GK5210@localhost.localdomain \
--to=kostix+git@007spb.ru \
--cc=git@vger.kernel.org \
--cc=henryzhang62@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.