git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: About Summer of code idea -- better big-file support

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Mar 19, 2011, 15:13 UTC
Message-ID
<AANLkTimH9pgO7JxN3vOcN=Kb3QGpbM7OO4bMpL2eAs=3@mail.gmail.com>
In-Reply-To
<AANLkTikp5GS0gnqLVgZY4E0wBDmQBp1iftOON3MSMHea@mail.gmail.com>
2011/3/19 徐迪 <xudifsd@gmail.com>:
Show 10 quoted lines
> 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
Previous: 徐迪Next: 徐迪
Message 4 of 5 in “About Summer of code idea -- better big-file support”
  1. 徐迪Mar 19, 2011
  2. Nguyen Thai Ngoc DuyMar 19, 2011
  3. 徐迪Mar 19, 2011
  4. Nguyen Thai Ngoc DuyMar 19, 2011
  5. 徐迪Mar 20, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.