From: Jakub Narebski <jnareb@gmail.com>
To: Kai Blin <kai@samba.org>
Cc: David Symonds <dsymonds@gmail.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Tim Ansell <mithro@mithis.com>
Subject: Re: How it was at GitTogether'08 ?
Date: Sun, 9 Nov 2008 17:31:47 +0100 [thread overview]
Message-ID: <200811091731.48694.jnareb@gmail.com> (raw)
In-Reply-To: <200811091636.55343.kai@samba.org>
On Sun, 9 Nov 2008, Kai Blin wrote:
> 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.
What I meant here (but perhaps was not clear) was (ab)using submodules
to allow to have full working repository without large [media] files
both in object database (repository) and without them checked out.
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).
As to submodules UI and GUI support for submodules... currently it is
unfortunately lacking.
Note that I explicitly mentioned that (ab)using submodules to better
deal with large files is _workaround_, and not _solution_. Lazy clone
in version proposed by Tim is IMHO correct solution.
P.S. Could anybody document at last `delta' gitattribute?
P.P.S. You can have separate diff driver for binary files, but I don't
know anyone who uses for example some such for images...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-11-09 16:33 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 [this message]
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=200811091731.48694.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=kai@samba.org \
--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 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).