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

Re: How it was at GitTogether'08 ?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 10, 2008, 12:09 UTC
Message-ID
<alpine.DEB.1.00.0811101307250.30769@pacific.mpi-cbg.de>
In-Reply-To
<200811101109.02885.kai@samba.org>
Hi,
On Mon, 10 Nov 2008, Kai Blin wrote:
Show 19 quoted lines
> On Monday 10 November 2008 10:58:05 Johannes Schindelin wrote:
> 
> > > 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.
> 
> Ok, I agree. But you could work around that by teaching the artists to 
> fetch/rebase/push instead of just pushing, or hiding this in the GUI. If 
> there's a conflict on a binary data file you're screwed anyway. :)

A fetch in that case would make the artist download things she does not need, right? So maybe that is not the way to go.

Show 9 quoted lines
> > 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.
> 
> Incidentally I'm currently working on something like this, just aimed at 
> the "artist side", instead of the VCS side. This certainly is a useable 
> solution for artists.
Seems like a nice starting point for a git-gui-in-a-browser.
> But at some point a developer will want to check out the repository to 
> cut a release tarball, and we're back to wanting shallow and narrow 
> clones. :)
Shallow clones are not an issue.  They _should_ work.
And for releasing you do not want narrow clones.

Ciao, Dscho

Previous: Kai BlinNext: Johannes Schindelin
Message 13 of 29 in “How it was at GitTogether'08 ?”
  1. Jakub NarebskiNov 8, 2008
  2. Johan HerlandNov 8, 2008
  3. Jeff KingNov 8, 2008
  4. David SymondsNov 8, 2008
  5. Jakub NarebskiNov 8, 2008
  6. Kai BlinNov 9, 2008
  7. Jakub NarebskiNov 9, 2008
  8. Kai BlinNov 9, 2008
  9. Jakub NarebskiNov 10, 2008
  10. Kai BlinNov 10, 2008
  11. Johannes SchindelinNov 10, 2008
  12. Kai BlinNov 10, 2008
  13. Johannes SchindelinNov 10, 2008
  14. Johannes SchindelinNov 10, 2008
  15. Jakub NarebskiNov 10, 2008
  16. Jakub NarebskiNov 9, 2008
  17. Steven GrimmNov 9, 2008
  18. Jakub NarebskiNov 9, 2008
  19. Robin RosenbergNov 9, 2008
  20. Shawn O. PearceNov 9, 2008
  21. Steven GrimmNov 9, 2008
  22. Jakub NarebskiNov 9, 2008
  23. Jonas FonsecaNov 11, 2008
  24. Johannes SchindelinNov 11, 2008
  25. Shawn O. PearceNov 9, 2008
  26. Jakub NarebskiNov 9, 2008
  27. Tim AnsellNov 10, 2008
  28. Jean-Luc HerrenNov 9, 2008
  29. Junio C HamanoNov 11, 2008

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.