From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Jeff King <peff@peff.net>,
Sergio Callegari <sergio.callegari@gmail.com>,
Bo Chen <chen@chenirvine.org>,
git@vger.kernel.org
Subject: Re: GSoC - Some questions on the idea of
Date: Wed, 11 Apr 2012 11:44:23 -0500 [thread overview]
Message-ID: <4F85B4E7.7090603@gmail.com> (raw)
In-Reply-To: <20120411060357.GA15805@burratino>
On 4/11/2012 1:04 AM, Jonathan Nieder wrote:
> Neal Kreitzinger wrote:
>
>> Maybe small binaries do xdelta well and the above is a moot point.
>
> If I am reading it correctly, diff-delta copes fine with smallish
> binary files that have not changed much.
>
> I would suggest tracking source code instead of binaries if
> possible, though.
>
I suppose the original "source" in git (linux kernel) was so low level
that it had no graphics files. However, most projects are end-user
projects and have graphics so I would think that tracking them is a
normal expected use of git to version your software. If you're going to
do that then there shouldn't be a problem tracking other binaries that
are static constants across all servers (as opposed to user edited
content like databases). I would consider this subset of "binaries" to
be the expected domain of git revision control for software, ie, gui
software. Graphics files for your app are "source". The binary is all
you have. It's the "source" that you edit to make changes.
Maybe I'm missing something here. Maybe graphics files are "container"
files and that makes them a problem.
v/r,
neal
next prev parent reply other threads:[~2012-04-11 16:44 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 4:38 GSoC - Some questions on the idea of "Better big-file support" Bo Chen
2012-03-28 6:19 ` Nguyen Thai Ngoc Duy
2012-03-28 11:33 ` GSoC - Some questions on the idea of Sergio
2012-03-30 19:44 ` Bo Chen
2012-03-30 19:51 ` Bo Chen
2012-03-30 20:34 ` Jeff King
2012-03-30 23:08 ` Bo Chen
2012-03-31 11:02 ` Sergio Callegari
2012-03-31 16:18 ` Neal Kreitzinger
2012-04-02 21:07 ` Jeff King
2012-04-03 9:58 ` Sergio Callegari
2012-04-11 1:24 ` Neal Kreitzinger
2012-04-11 6:04 ` Jonathan Nieder
2012-04-11 16:29 ` Neal Kreitzinger
2012-04-11 22:09 ` Jeff King
2012-04-11 16:35 ` Neal Kreitzinger
2012-04-11 16:44 ` Neal Kreitzinger [this message]
2012-04-11 17:20 ` Jonathan Nieder
2012-04-11 18:51 ` Junio C Hamano
2012-04-11 19:03 ` Jonathan Nieder
2012-04-11 18:23 ` Neal Kreitzinger
2012-04-11 21:35 ` Jeff King
2012-04-12 19:29 ` Neal Kreitzinger
2012-04-12 21:03 ` Jeff King
[not found] ` <4F8A2EBD.1070407@gmail.com>
2012-04-15 2:15 ` Jeff King
2012-04-15 2:33 ` Neal Kreitzinger
2012-04-16 14:54 ` Jeff King
2012-05-10 21:43 ` Neal Kreitzinger
2012-05-10 22:39 ` Jeff King
2012-04-12 21:08 ` Neal Kreitzinger
2012-04-13 21:36 ` Bo Chen
2012-03-31 15:19 ` Neal Kreitzinger
2012-04-02 21:40 ` Jeff King
2012-04-02 22:19 ` Junio C Hamano
2012-04-03 10:07 ` Jeff King
2012-03-31 16:49 ` Neal Kreitzinger
2012-03-31 20:28 ` Neal Kreitzinger
2012-03-31 21:27 ` Bo Chen
2012-04-01 4:22 ` Nguyen Thai Ngoc Duy
2012-04-01 23:30 ` Bo Chen
2012-04-02 1:00 ` Nguyen Thai Ngoc Duy
2012-03-30 19:11 ` GSoC - Some questions on the idea of "Better big-file support" Bo Chen
2012-03-30 19:54 ` Jeff King
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=4F85B4E7.7090603@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=chen@chenirvine.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=sergio.callegari@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 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.