All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Blin <kai@samba.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jakub Narebski <jnareb@gmail.com>,
	David Symonds <dsymonds@gmail.com>,
	git@vger.kernel.org, Tim Ansell <mithro@mithis.com>
Subject: Re: How it was at GitTogether'08 ?
Date: Mon, 10 Nov 2008 11:08:51 +0100	[thread overview]
Message-ID: <200811101109.02885.kai@samba.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0811101055020.30769@pacific.mpi-cbg.de>

[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]

On Monday 10 November 2008 10:58:05 Johannes Schindelin wrote:
Hi Dscho,

> > 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. :)

> 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. 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. :)

Cheers,
Kai

-- 
Kai Blin
WorldForge developer  http://www.worldforge.org/
Wine developer        http://wiki.winehq.org/KaiBlin
Samba team member     http://www.samba.org/samba/team/
--
Will code for cotton.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-11-10 10:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08  1:54 How it was at GitTogether'08 ? Jakub Narebski
2008-11-08  3:41 ` Johan Herland
2008-11-08 14:17   ` Jeff King
2008-11-08  5:08 ` David Symonds
2008-11-08 15:31   ` Jakub Narebski
2008-11-09 15:36     ` Kai Blin
2008-11-09 16:31       ` Jakub Narebski
2008-11-09 18:55         ` Kai Blin
2008-11-10  9:30           ` Large media in git (was: How it was at GitTogether'08)? Jakub Narebski
2008-11-10 10:13             ` Kai Blin
2008-11-10  9:58           ` How it was at GitTogether'08 ? Johannes Schindelin
2008-11-10 10:08             ` Kai Blin [this message]
2008-11-10 12:09               ` Johannes Schindelin
2008-11-10 10:38     ` Johannes Schindelin
2008-11-10 11:36       ` Jakub Narebski
2008-11-09 11:49 ` Jakub Narebski
2008-11-09 16:52   ` Steven Grimm
2008-11-09 17:54     ` Jakub Narebski
2008-11-09 18:58     ` Robin Rosenberg
2008-11-09 19:55       ` Shawn O. Pearce
2008-11-09 21:58         ` Steven Grimm
2008-11-09 23:52           ` Jakub Narebski
2008-11-11 22:05             ` Jonas Fonseca
2008-11-11 23:26               ` Johannes Schindelin
2008-11-09 19:54   ` Shawn O. Pearce
2008-11-09 22:03     ` Jakub Narebski
2008-11-10  3:32   ` Tim Ansell
2008-11-09 23:32 ` Jean-Luc Herren
2008-11-11 21:35 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200811101109.02885.kai@samba.org \
    --to=kai@samba.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=mithro@mithis.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.