From: Linus Torvalds <torvalds@linux-foundation.org>
To: Martin Waitz <tali@admingilde.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Anton Tropashko <atropashko@yahoo.com>,
git@vger.kernel.org
Subject: Re: Errors cloning large repo
Date: Sat, 10 Mar 2007 14:46:35 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703101443411.10330@woody.linux-foundation.org> (raw)
In-Reply-To: <20070310223251.GA20726@admingilde.org>
On Sat, 10 Mar 2007, Martin Waitz wrote:
>
> On Sat, Mar 10, 2007 at 01:01:44AM -0500, Shawn O. Pearce wrote:
> > Its very likely this did fit in just under 4 GiB of packed data,
> > but as you said, without O_LARGEFILE we can't work with it.
>
> but newer git version can cope with it:
>
> -r--r--r-- 1 martin martin 3847536413 18. Feb 10:36 pack-ffe867679d673ea5fbfa598b28aca1e58528b8cd.pack
Are you sure you're not just running a 64-bit process?
64-bit processes don't need O_LARGEFILE to process files larger than 2GB,
since for them, off_t is already 64-bit.
Grepping for O_LARGEFILE shows nothing.
Oh, except we have that
#define _FILE_OFFSET_BITS 64
which is just a horrible hack. That's nasty. We should just use
O_LARGEFILE rather than depend on some internal glibc thing that works
nowhere else.
Linus
next prev parent reply other threads:[~2007-03-10 22:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 2:37 Errors cloning large repo Anton Tropashko
2007-03-10 3:07 ` Shawn O. Pearce
2007-03-10 5:54 ` Linus Torvalds
2007-03-10 6:01 ` Shawn O. Pearce
2007-03-10 22:32 ` Martin Waitz
2007-03-10 22:46 ` Linus Torvalds [this message]
2007-03-11 21:35 ` Martin Waitz
2007-03-10 10:27 ` Jakub Narebski
2007-03-11 2:00 ` Shawn O. Pearce
2007-03-12 11:09 ` Jakub Narebski
2007-03-12 14:24 ` Shawn O. Pearce
2007-03-17 13:23 ` Jakub Narebski
[not found] ` <82B0999F-73E8-494E-8D66-FEEEDA25FB91@adacore.com>
2007-03-10 22:21 ` Linus Torvalds
2007-03-10 5:10 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2007-03-13 0:02 Anton Tropashko
2007-03-12 17:39 Anton Tropashko
2007-03-12 18:40 ` Linus Torvalds
2007-03-10 1:21 Anton Tropashko
2007-03-10 1:45 ` Linus Torvalds
2007-03-09 23:48 Anton Tropashko
2007-03-10 0:54 ` Linus Torvalds
2007-03-10 2:03 ` Linus Torvalds
2007-03-10 2:12 ` Junio C Hamano
2007-03-09 19:20 Anton Tropashko
2007-03-09 21:37 ` Linus Torvalds
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=Pine.LNX.4.64.0703101443411.10330@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=atropashko@yahoo.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=tali@admingilde.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).