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

Re: Better big file support & GSoC

From
JMJonathan Michalon <johndescs@gmail.com>
Date
Apr 4, 2011, 16:52 UTC
Message-ID
<20110404185248.1061e452@RunningPinguin.chalmion.homelinux.net>
In-Reply-To
<alpine.DEB.2.00.1104022056530.29543@asgard.lang.hm>

Le Sat, 2 Apr 2011 21:00:53 -0700 (PDT), david@lang.hm a écrit :

Show 15 quoted lines
> On Sat, 2 Apr 2011, Jonathan Michalon wrote:
> 
> > Hi Git people,
> >
> > I'm an applicant to the GSoC within git.
> > I would like to help building a better big file support mechanism.
> >
> > I have read the latest threads on this topic:
> > http://thread.gmane.org/gmane.comp.version-control.git/165389/focus=165389
> > http://thread.gmane.org/gmane.comp.version-control.git/168403/focus=168852
> 
> there was also an offshoot of a similar discussion that pointed out that 
> this could be done pretty cleanly with the clean/smudge hooks.
> 
> David Lang

Edit: Hum I just failed to reply correcly... did only to the original poster, not the whole list. My apologies.

Message: At least to my mind big file support is more important than just doing some tricky manipulation with existing hook types. It should highly benefit from being integrated deeply within git, both because of optimisations or in terms of integration. I read the discussion about clean/smudge hooks too but I skipped the idea because the final thought was "feels like a hack". See here: http://article.gmane.org/gmane.comp.version-control.git/168857

In fact I don't know how this could be considered as "clean" or "hacky"…

-- Jonathan Michalon

Previous: david@lang.hm
Message 5 of 5 in “Better big file support & GSoC”
  1. Jonathan MichalonApr 2, 2011
  2. Carlos Martín NietoApr 2, 2011
  3. Jonathan MichalonApr 4, 2011
  4. david@lang.hmApr 3, 2011
  5. Jonathan MichalonApr 4, 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.