Hi, On Sun, 9 Nov 2008, Kai Blin wrote: > On Sunday 09 November 2008 17:31:47 Jakub Narebski wrote: > > > The workaround is to put all large files for example in 'media/' > > folder, and make this folder be submodule. Each clone of repository > > can have this 'media' submodule either present (both in object > > database, although usually separate from main project object > > database), or not present (not cloned and not checked out). > > Tim was talking about that media/ folder and managing that in git. If > you want to work on the media, you might end up getting hundreds of > gigabytes of data to get that folder, even if you only need to change > one single file. > > That's the issue we're running into, and I don't thing submodules solve > this at all. You'd have to have a single repository for each and every media file, and you'd need to use shallow clones and shallow fetches. However, a push-conflict will probably be beyond any non-programmer skillz. I'd rather propose to have a different interface, like through a web server, where the user can say "I have some cool new graphics, in this .zip file" together with a commit message. Kind of a git-gui via browser. Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
