git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Henry Huang <henry.s.huang@gmail.com>
Cc: Nanako Shiraishi <nanako3@lavabit.com>, git@vger.kernel.org
Subject: Re: [SoC RFC] about "restartable clone"
Date: Mon, 16 Feb 2009 08:00:01 -0800	[thread overview]
Message-ID: <20090216160001.GC18525@spearce.org> (raw)
In-Reply-To: <20090215203714.6117@nanako3.lavabit.com>

Nanako Shiraishi <nanako3@lavabit.com> wrote:
> Quoting Henry Huang <henry.s.huang@gmail.com>:
> 
> > Now i have several problems:
> >
> > 1) Less familiar with git source code
> > 2) Less experience in Open Source Development
> > 3) No proposal for this project
> >
> > My questions:
> >
> > 1) Are there any documents for git's internals ?-- (.git/ structure,
> > data structures: DAG of objects,
> > branches, tags, index etc.) and workflow of main operations
> >
> > 2) Could anyone give me some hints -- where to begin with this project?
> 
> A good starting point would be to download the source and look at the files in Documentation directory, including its technical subdirectory. The information in these files would answer large part of your questions in 1).

Also, the Git Community Book (http://book.git-scm.com/) chapter
7 "Internals and Plumbing" has some really nice detail on this.
I'm not sure it fully covers the algorithms used to generate a
pack file, but it does cover the data structures involved in
detail, with pretty graphics to help explain it.  Scott has done
a wonderful job editing this text.

-- 
Shawn.

      reply	other threads:[~2009-02-16 16:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14  2:38 [SoC RFC] about "restartable clone" Henry Huang
2009-02-15 11:37 ` Nanako Shiraishi
2009-02-16 16:00   ` Shawn O. Pearce [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=20090216160001.GC18525@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=henry.s.huang@gmail.com \
    --cc=nanako3@lavabit.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;
as well as URLs for NNTP newsgroup(s).