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

Re: GSoC - Some questions on the idea of

From
NKNeal Kreitzinger <nkreitzinger@gmail.com>
Date
Apr 12, 2012, 19:29 UTC
Message-ID
<4F872D24.8010609@gmail.com>
In-Reply-To
<20120411213522.GA28199@sigill.intra.peff.net>
On 4/11/2012 4:35 PM, Jeff King wrote:
Show 17 quoted lines
> On Tue, Apr 10, 2012 at 08:24:48PM -0500, Neal Kreitzinger wrote:
>
>> This is all theory to me, but the reality is looming over my head
>> since most of the components I should be tracking are binaries small
>> (large history?) and big (but am not yet because of "big-file"
>> concerns -- I don't want to have to refactor my vast git ecosystem
>> with filter branch later because I slammed binaries into the main
>> project or superproject without proper systems programming (I'm not
>> sure what the c/linux term is for 'systems programming', but in the
>> mainframe world it meant making sure everything was configured for
>> efficient performance)).
> So properly implemented, no, you would not have to ever filter-branch to
> tweak these settings. You might have to do a repack to see the gains
> (because you want to delete the old non-split representation you have in
> your pack and replace it with a split representation), but that is
> transparent to git's abstract data model.
>

I'm likely going to have to slam graphics files into the main repo in the very near future. It sounds like once git.git is updated for big-file optimization I can just upgrade to that git version and repack to get the benefits. Any idea when that version of git will come out release number wise and calendar wise?

(Don't read this next part if you just ate or are eating or drinking. You may throw-up from nausea or choke from laughing.) (I am forced to deal with a mandated/micromanaged change control menu design from the powers-that-be that is based on cvs workflow and to wipe-your-nose-for-you. It can't even cope with branches much less submodules so in that context there isn't time to implement the graphics tracking as a submodule. This change control menu is designed to replace cvs commands with equivalent-results git-command sequences. While there are many git users who import from svn into git, do their work in git, and then export back into svn to get work done, ironically I am probably the only git user who has to import from git (powers-that-be mandated cvs-style menu controlled git-repo) into git (separate normal git repo and commandline), do the work in normal git, and then export it back into git (cvs-style menu controlled git-repo).)

v/r, neal

Previous: Jeff KingNext: Jeff King
Message 23 of 43 in “GSoC - Some questions on the idea of "Better big-file support".”
  1. Bo ChenMar 28, 2012
  2. Nguyen Thai Ngoc DuyMar 28, 2012
  3. SergioMar 28, 2012
  4. Bo ChenMar 30, 2012
  5. Bo ChenMar 30, 2012
  6. Jeff KingMar 30, 2012
  7. Bo ChenMar 30, 2012
  8. Sergio CallegariMar 31, 2012
  9. Neal KreitzingerMar 31, 2012
  10. Jeff KingApr 2, 2012
  11. Sergio CallegariApr 3, 2012
  12. Neal KreitzingerApr 11, 2012
  13. Jonathan NiederApr 11, 2012
  14. Neal KreitzingerApr 11, 2012
  15. Jeff KingApr 11, 2012
  16. Neal KreitzingerApr 11, 2012
  17. Neal KreitzingerApr 11, 2012
  18. Jonathan NiederApr 11, 2012
  19. Junio C HamanoApr 11, 2012
  20. Jonathan NiederApr 11, 2012
  21. Neal KreitzingerApr 11, 2012
  22. Jeff KingApr 11, 2012
  23. Neal KreitzingerApr 12, 2012
  24. Jeff KingApr 12, 2012
  25. Neal KreitzingerApr 12, 2012
  26. Bo ChenApr 13, 2012
  27. Neal KreitzingerMar 31, 2012
  28. Jeff KingApr 2, 2012
  29. Junio C HamanoApr 2, 2012
  30. Jeff KingApr 3, 2012
  31. Neal KreitzingerMar 31, 2012
  32. Neal KreitzingerMar 31, 2012
  33. Bo ChenMar 31, 2012
  34. Nguyen Thai Ngoc DuyApr 1, 2012
  35. Bo ChenApr 1, 2012
  36. Nguyen Thai Ngoc DuyApr 2, 2012
  37. Bo ChenMar 30, 2012
  38. Jeff KingMar 30, 2012
  39. Jeff KingApr 15, 2012
  40. Neal KreitzingerApr 15, 2012
  41. Jeff KingApr 16, 2012
  42. Neal KreitzingerMay 10, 2012
  43. Jeff KingMay 10, 2012

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.