git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ryanzec <basire@gmail.com>
To: git@vger.kernel.org
Subject: Git and Binary Files
Date: Thu, 28 Apr 2011 08:11:16 -0700 (PDT)	[thread overview]
Message-ID: <1304003476678-6313601.post@n2.nabble.com> (raw)

I am a long time user of SVN and while it has worked for me in the past, I
always felt like there were features I wasn't using properly. Branching is
one of those features. Most of the time when I created branches, I was
really creating tags because when I created branches, I never really used
them for merging, just more to take a snapshot of the current code. When I
did have to make changes to code in one branch and merge them to another, I
always just manually merged the files because it was usually 1 or two files
and merge with SVN from what I hear is not a straight forward process. I
have recently starting using merging at work with SVN and I now really
understanding why people try to avoid it in SVN. Another thing I do in SVN
that I fell is counter productive is I only commit when I am 100% complete
with a feature. It would be great to commit things in chunks instead of one
great big change. I have had multiple times where I was like "I wish I could
go back just a little bit in time" but of course I have to go back to the
initial version which may be a week old or modify the file manually to get
back to the state I want it at (which it was I usually do).

Thankfully I have been introduced to the world of DVCS, specifically git. My
work is in the process of porting over to it and as I have been learning it,
I am wondering why I am still using SVN. Git fixes the above issues as well
as also having a number of cool little features.

Now while it fixes a lot of things there is one feature that concerns me
with trying to using it for game development projects and that is how it
handles binary files. In my day job, that is not a huge concern as I do web
development and I don't deal with many binary files that need to be
versioned. Images are the only ones and they rarely change and are not
usually that big. Game development is a different story. Game development in
general has many binary files (images, 3d assets, sound files, etc...).
Since git generally has a copy of the entire binary file for each change
that happens to it and since these assets can change quite often and
sometimes be large in size, I have a feeling that it can make the repository
of project become huge even with the compression that git does with git
pack/git gc.

Does anyone use git with game development? What is the workflow for binary
assets? Do you just store them in git (if so, are they in the main
repository or a separate repository using submodules)? If you don't include
binaries in the git repository, what tool do you use to manage binary assets
and does it work well with git?

--
View this message in context: http://git.661346.n2.nabble.com/Git-and-Binary-Files-tp6313601p6313601.html
Sent from the git mailing list archive at Nabble.com.

             reply	other threads:[~2011-04-28 15:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 15:11 ryanzec [this message]
2011-04-28 15:26 ` Git and Binary Files Peter Jönsson P
  -- strict thread matches above, loose matches on Subject: below --
2010-07-28 14:17 git and binary files Jan Dittmer
2010-07-28 14:29 ` Matthieu Moy
2010-07-28 20:17   ` Avery Pennarun
2008-01-16 10:34 Petko Manolov
2008-01-16 10:54 ` David Symonds
2008-01-16 13:21   ` Petko Manolov
2008-01-16 13:42     ` Johannes Schindelin
2008-01-16 13:58       ` Petko Manolov
2008-01-16 14:07         ` Johannes Schindelin
2008-01-16 14:21           ` Petko Manolov
2008-01-16 14:34         ` Wincent Colaiuta
2008-01-16 14:45           ` Petko Manolov
2008-01-16 18:02             ` Junio C Hamano
2008-01-16 18:09               ` Junio C Hamano
2008-01-16 11:54 ` Johannes Schindelin
2008-01-16 13:39   ` Petko Manolov
2008-01-16 13:53     ` Jakub Narebski
2008-01-16 14:04       ` Petko Manolov
2008-01-16 14:20         ` Jakub Narebski
2008-01-16 14:43           ` Petko Manolov
2008-01-16 15:01             ` Nicolas Pitre
2008-01-16 15:18               ` Petko Manolov
2008-01-16 15:58                 ` Nicolas Pitre
2008-01-16 16:06                   ` Petko Manolov
2008-01-16 16:09               ` Petko Manolov
2008-01-16 16:34             ` Jakub Narebski
2008-01-16 16:41             ` Florian Weimer
2008-01-16 13:54     ` Jeff King
2008-01-16 14:14       ` Petko Manolov
2008-01-16 14:18         ` Jeff King
2008-01-16 14:25           ` Petko Manolov
2008-01-16 14:32             ` Jeff King
2008-01-16 14:39               ` Petko Manolov
2008-01-16 15:05                 ` Rogan Dawes
2008-01-18  6:52                 ` David Brown

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=1304003476678-6313601.post@n2.nabble.com \
    --to=basire@gmail.com \
    --cc=git@vger.kernel.org \
    /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).