From: John <john@puckerupgames•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: Nicolas Pitre <nico@fluxnic•net>, Jeff King <peff@peff•net>,
git@vger•kernel.org
Subject: Re: serious performance issues with images, audio files, and other "non-code" data
Date: Mon, 24 May 2010 03:01:37 -0400 [thread overview]
Message-ID: <4BFA2451.6090507@puckerupgames.com> (raw)
In-Reply-To: <7vaarq14me.fsf@alter.siamese.dyndns.org>
Ok, fair enough. It's your project, and you are defining "source control" as
that which git supports: non-binary, line-by-line text only, C, bash .. no
images, documents, etc.
I only wish that definition of "source" had been more clear from the get-go.
Perhaps a front and center blurb on the git home page or mission statement might
clarify things for those of us who have different definitions of "source"? That
way, you wouldn't have to be bothered by folks trying to version all their
project assets with git. For example, you could specify that non-text is out of
scope for git, (or however you wish to define "source").
On 05/23/2010 09:16 PM, Junio C Hamano wrote:
> John<john@puckerupgames•com> writes:
>
>> Is there any reason why someone would NOT want the above
>> ".gitattributes" defined by default?
>
> Other than that our originally intended target audience are people who use
> git as a source code control system, not much.
>
next prev parent reply other threads:[~2010-05-24 7:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 18:53 serious performance issues with images, audio files, and other "non-code" data John
2010-05-12 19:15 ` Jakub Narebski
2010-05-14 5:10 ` Jeff King
2010-05-14 12:54 ` John
2010-05-14 17:26 ` Dirk Süsserott
2010-05-17 23:16 ` Jeff King
2010-05-17 23:33 ` Sverre Rabbelier
2010-05-18 19:07 ` Jeff King
2010-05-18 19:10 ` Sverre Rabbelier
2010-05-18 19:27 ` Jeff King
2010-05-18 19:37 ` Nicolas Pitre
2010-05-18 18:50 ` John
2010-05-18 18:54 ` Sverre Rabbelier
2010-05-18 19:19 ` Jeff King
2010-05-18 19:33 ` Nicolas Pitre
2010-05-18 19:41 ` Jeff King
2010-05-18 19:59 ` Nicolas Pitre
2010-05-24 0:21 ` John
2010-05-24 1:16 ` Junio C Hamano
2010-05-24 7:01 ` John [this message]
2010-05-25 6:33 ` Jeff King
2010-05-25 7:28 ` Michael J Gruber
2010-05-25 16:12 ` John
2010-05-25 17:18 ` Nicolas Pitre
2010-05-25 17:47 ` John
2010-05-24 5:39 ` Jeff King
2010-05-24 6:44 ` John
2010-05-24 6:45 ` 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=4BFA2451.6090507@puckerupgames.com \
--to=john@puckerupgames$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=nico@fluxnic$(echo .)net \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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