From: 徐迪 <xudifsd@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: "Git 邮件列表" <git@vger.kernel.org>
Subject: Re: About Summer of code idea -- better big-file support
Date: Sun, 20 Mar 2011 20:33:50 +0800 [thread overview]
Message-ID: <AANLkTimTWLqkaFkiruqZ8FU8y3YX9C4ujPOPTTJzdRtk@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimH9pgO7JxN3vOcN=Kb3QGpbM7OO4bMpL2eAs=3@mail.gmail.com>
2011/3/19 Nguyen Thai Ngoc Duy <pclouds@gmail.com>:
> 2011/3/19 徐迪 <xudifsd@gmail.com>:
>> 2011/3/19, Nguyen Thai Ngoc Duy <pclouds@gmail.com>:
>>> See below link for recent discussions regarding big file support:
>>>
>>> http://thread.gmane.org/gmane.comp.version-control.git/165389/focus=168956
>>>
>>> On the store of big files, bup (at github) model might fit in as well
>>> if large files change a small portion regularly.
>>>
>> But, why those features haven't merged into upstream developement?
>> Sorry for this question, but I'm fresh here.
>
> This is just my guess. For specific apps, you should pull their authors in.
>
> All apps experiment different ways of dealing with big files and work
> in certain situations. None is generic enough to be merged upstream.
> Take bup as an example, it aims at big files _only_. A file is treated
> as a directory of many smaller pieces. In order to get it merged, we
> need to separate those big files from the rest because it's just too
> different in handling them.
> --
> Duy
>
Thanks for that timely link, I think I should do some more research now :P
prev parent reply other threads:[~2011-03-20 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 13:15 About Summer of code idea -- better big-file support 徐迪
2011-03-19 13:48 ` Nguyen Thai Ngoc Duy
2011-03-19 14:28 ` 徐迪
2011-03-19 15:13 ` Nguyen Thai Ngoc Duy
2011-03-20 12:33 ` 徐迪 [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=AANLkTimTWLqkaFkiruqZ8FU8y3YX9C4ujPOPTTJzdRtk@mail.gmail.com \
--to=xudifsd@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@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.
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).