From: Bill Lear <rael@zopyra.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: "Johan 't Hart" <johanthart@gmail.com>,
"Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com>,
Thomas Johnson <thomas.j.johnson@gmail.com>,
git@vger.kernel.org
Subject: Re: Git as electronic lab notebook
Date: Sat, 19 Dec 2009 22:43:11 -0600 [thread overview]
Message-ID: <19245.43871.588697.532035@lisa.zopyra.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0912192212400.28241@xanadu.home>
On Saturday, December 19, 2009 at 22:15:00 (-0500) Nicolas Pitre writes:
>On Sun, 20 Dec 2009, Johan 't Hart wrote:
>
>> Is git able to handle 4Gig files? I've heard git loads every file completely
>> in memory before handling it...
>
>Right. Sowith current Git you will be able to deal with 4GB files only
>if you have a 64-bit machine and more than 4GB of RAM.
??
% uname -a
Linux pppp 2.6.31.6-166.fc12.i686 #1 SMP Wed Dec 9 11:14:59 EST 2009 i686 i686 i386 GNU/Linux
% cat /proc/meminfo | grep MemTotal
MemTotal: 3095296 kB
% mkdir gogle
% cd gogle
% git init
% dd if=/dev/zero of=zerofile.tst bs=1k count=4700000
% git add *
% git commit -a -m new
[master (root-commit) 35a25be] new
1 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 zerofile.tst
% git --version
git version 1.6.5.7
Seems ok to me...
Though, I find this interesting:
% git log -p
commit 35a25be3fff2f8bbd6ec22c94b9a5c0d66053d21
Author: Bill Lear <rael@zopyra.com>
Date: Sat Dec 19 22:38:48 2009 -0600
new
diff --git a/zerofile.tst b/zerofile.tst
new file mode 100644
index 0000000..e5bd39d
Binary files /dev/null and b/zerofile.tst differ
Bill
next prev parent reply other threads:[~2009-12-20 4:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 12:23 Git as electronic lab notebook Thomas Johnson
2009-12-19 13:38 ` Ciprian Dorin, Craciun
2009-12-20 0:15 ` Johan 't Hart
2009-12-20 3:15 ` Nicolas Pitre
2009-12-20 4:43 ` Bill Lear [this message]
2009-12-20 4:55 ` Nicolas Pitre
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=19245.43871.588697.532035@lisa.zopyra.com \
--to=rael@zopyra.com \
--cc=ciprian.craciun@gmail.com \
--cc=git@vger.kernel.org \
--cc=johanthart@gmail.com \
--cc=nico@fluxnic.net \
--cc=thomas.j.johnson@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