list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: ZheNing Hu <>
To: Jiang Xin <>
Cc: Git List <>,
	Junio C Hamano <>,
	Denton Liu <>,
	Hariom verma <>,
	Christian Couder <>,
	Eric Sunshine <>,
	Jeff King <>
Subject: Re: [GSoC] Hello Git
Date: Thu, 20 May 2021 15:21:43 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Jiang Xin <> 于2021年5月19日周三 下午3:19写道:
> > I'm ZheNing Hu, I am very lucky to participate in the GSoC
> > git project this year. Many people in the git community already
> > have given me a lot of help in the past few months.
> > Junio, Christian, Peff, Eric, Denton..., it's great to get along with
> > you guys! Your review and guidance have greatly benefited
> > my growth.
> I admire you so much that you can join the open source community at a
> very young age. I will continue to offer my help both online and
> offline, in your favorite language (Chinese of course).

Participating in open source is a very fun thing! Thanks for your help haha!

> > In these days before GSoC, I learned some simple command
> > implementation and data structures of git, learned strict coding
> > standards and learned how to test, More importantly, I learned how
> > to communicate with these kind-hearted reviewers.
> >
> > Of course, there are still many difficulties for me:
> > * My poor English sometimes can’t express the meaning clearly.
> There are too many differences between English and Chinese, but don't
> worry. Remember, practice is perfect. You can also practice your
> English by reviewing Git l10n in Chinese, see: "po/".

I have noticed that the language translation comparison table is in *.po,
which really helps me a lot sometimes.

> > ### The connection between Git and the file system
> >
> > I am currently studying operating system course, git as a
> > file system on top of the file system.
> > There are many differences and similarities with ordinary
> > file systems. I am very curious about this knowledge, do
> > not know if there are any relevant reading materials?
> Git objects are stored in ".git/objects" directory in two forms: loose
> object and packfile.  These two types of files are deflated in zlib
> format. In order to increase the speed of traversing these objects in
> this object store, many meta files are created. For example, index
> files and reverse index files for packfiles, bitmap file, commit-graph
> files, etc.
> Docs for these files:
>  * Documentation/technical/pack-format.txt
>  * Documentation/technical/index-format.txt
>  * Documentation/technical/chunk-format.txt
>  * Documentation/technical/multi-pack-index.txt
>  * Documentation/technical/bitmap-format.txt
>  * Documentation/technical/commit-graph-format.txt
>  * Documentation/technical/commit-graph.txt

This is what I want to know: how git objects are stored!
This can help me understand git itself at a deeper level.

> --
> Jiang Xin

ZheNing Hu

      reply	other threads:[~2021-05-20  7:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  6:40 ZheNing Hu
2021-05-18 14:32 ` Christian Couder
2021-05-20  7:14   ` ZheNing Hu
2021-05-20  8:00     ` Christian Couder
2021-05-20  8:09       ` ZheNing Hu
2021-05-20 14:59         ` Christian Couder
2021-05-19  7:19 ` Jiang Xin
2021-05-20  7:21   ` ZheNing Hu [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this inbox:

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 read-only IMAP folder(s) and NNTP newsgroup(s).