From: Duy Nguyen <pclouds@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: "Thomas Gummerer" <t.gummerer@gmail.com>,
"Matheus Tavares Bernardino" <matheus.bernardino@usp.br>,
git <git@vger.kernel.org>,
"Оля Тележная" <olyatelezhnaya@gmail.com>,
"Elijah Newren" <newren@gmail.com>,
"Tanushree Tumane" <tanushreetumane@gmail.com>,
"Jeff King" <peff@peff.net>
Subject: Re: Questions on GSoC 2019 Ideas
Date: Sun, 3 Mar 2019 17:17:02 +0700 [thread overview]
Message-ID: <CACsJy8A2e3e9JAAN8==PHxjO-5xki2NWLPb6vrFvCr8NLKmHyA@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8ATKdcDdbTzCdZFhChKEAWhjuYQJBpGXZ9HAVXK1r2pFw@mail.gmail.com>
On Sun, Mar 3, 2019 at 5:12 PM Duy Nguyen <pclouds@gmail.com> wrote:
> This is a good point. My guess is the pack access consists of two
> parts: deflate zlib, resolve delta objects (which is just another form
s/deflate/inflate/ (i keep making this mistake)
--
Duy
next prev parent reply other threads:[~2019-03-03 10:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 21:46 Questions on GSoC 2019 Ideas Matheus Tavares Bernardino
2019-02-28 22:07 ` Christian Couder
2019-03-01 9:30 ` Duy Nguyen
2019-03-02 15:09 ` Thomas Gummerer
2019-03-03 7:18 ` Christian Couder
2019-03-03 10:12 ` Duy Nguyen
2019-03-03 10:17 ` Duy Nguyen [this message]
2019-03-05 4:51 ` Jeff King
2019-03-05 12:57 ` Duy Nguyen
2019-03-05 23:46 ` Matheus Tavares Bernardino
2019-03-06 10:17 ` Duy Nguyen
2019-03-12 0:18 ` Matheus Tavares Bernardino
2019-03-12 10:02 ` Duy Nguyen
2019-03-12 10:11 ` Duy Nguyen
2019-04-04 1:15 ` Matheus Tavares Bernardino
2019-04-04 7:56 ` Christian Couder
2019-04-04 8:20 ` Mike Hommey
2019-04-05 16:28 ` Matheus Tavares Bernardino
2019-04-07 23:40 ` Christian Couder
2019-03-05 23:03 ` Matheus Tavares Bernardino
2019-03-06 23:17 ` Thomas Gummerer
2019-03-03 10:03 ` Duy Nguyen
2019-03-03 16:12 ` Thomas Gummerer
2019-03-01 15:20 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8A2e3e9JAAN8==PHxjO-5xki2NWLPb6vrFvCr8NLKmHyA@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=matheus.bernardino@usp.br \
--cc=newren@gmail.com \
--cc=olyatelezhnaya@gmail.com \
--cc=peff@peff.net \
--cc=t.gummerer@gmail.com \
--cc=tanushreetumane@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).