git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai Blin <kai@samba.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "David Symonds" <dsymonds@gmail.com>,
	git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: How it was at GitTogether'08 ?
Date: Sun, 9 Nov 2008 16:36:51 +0100	[thread overview]
Message-ID: <200811091636.55343.kai@samba.org> (raw)
In-Reply-To: <200811081631.06229.jnareb@gmail.com>

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

On Saturday 08 November 2008 16:31:04 Jakub Narebski wrote:

> > > * Tim: Git as a Media Repository
> > >  http://www.thousandparsec.net/~tim/media+git.pdf
> >
> > This has kicked off some mailing list discussion; I think this can be
> > a major weak point for git, since checking out only a subtree (and
> > only the latest revision) is the common SVN way, which copes with
> > media repositories and the like just fine.
>
> Well, you can workaround this weakness by (ab)using submodules...
> ...and one should always remember that casual partial checkouts
> interfere a bit with whole-tree commits.

Interesting. How would you use submodules to work around the fact that binary 
file changes diff very bad and produce huge histories with basically no value 
for the user of the working copy? Can you do this from a GUI, easily? We're 
talking about media repositories here, so our users are artists.

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-09 16:03 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 [this message]
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
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=200811091636.55343.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 \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).