From: Ehud Shabtai <eshabtai.lkml@gmail•com>
To: git@vger•kernel.org
Subject: trying to figure out this git thing - some questions
Date: Thu, 14 Apr 2005 22:02:21 +0300 [thread overview]
Message-ID: <68b6a2bc05041412025f1cb7c9@mail.gmail.com> (raw)
I'm trying to understand how it works and I'll appreciate if someone could help.
1. git uses object abstraction for the different types and so
everything is in one directory (objects). From what I've seen in the
implementation, the different kind of objects are not of the same type
(there aren't any operations which work on two different types) and
thus in each step when an object is used its type is verified.
What's the benefit of having them all in the same tree? An alternative
would be to separate the different object types into different
directories which trivially allows getting a list of all commits, or
trees or blobs.
2. A commit can have more than one parent. Can anyone draw an example
of such a case? When do we get a commit graph which is not linear?
3. How does git handle binary files? I guess it doesn't really care if
it's binary or text, but how would the diff and merge scripts handle
them?
next reply other threads:[~2005-04-14 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 19:02 Ehud Shabtai [this message]
2005-04-14 23:52 ` trying to figure out this git thing - some questions tony.luck
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=68b6a2bc05041412025f1cb7c9@mail.gmail.com \
--to=eshabtai.lkml@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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