From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Dana How <danahow@gmail.com>, Nicolas Pitre <nico@cam.org>,
Junio C Hamano <junkio@cox.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-{repack,pack-objects} accept --{pack,blob}-limit to control pack size
Date: Thu, 5 Apr 2007 09:21:33 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704050910590.6730@woody.linux-foundation.org> (raw)
In-Reply-To: <20070405155306.GI5436@spearce.org>
On Thu, 5 Apr 2007, Shawn O. Pearce wrote:
>
> Sure, OK, but that libc function doesn't exist on Mac OS X:
My bad. It's *not* linux-specific like the OSX man-page apparently says,
it's very traditional. But the right name is "lseek64()" (and offt64_t for
the size).
Of course, OSX didn't have some of the backwards-compatibility issues with
decades ago, so they just made off_t 64-bit by default. Maybe they don't
even bother to do the trivial portability things to support programs that
try to be portable..
Anyway, we should use open64(), lseek64() and friends to be as portable as
possible.. And if some system doesn't have them, just use the normal ops,
and pray that they are already 64-bit safe..
Linus
next prev parent reply other threads:[~2007-04-05 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 20:40 [PATCH] git-{repack,pack-objects} accept --{pack,blob}-limit to control pack size Dana How
2007-04-04 22:04 ` Nicolas Pitre
2007-04-04 22:55 ` Dana How
2007-04-05 3:17 ` Nicolas Pitre
2007-04-05 7:15 ` Shawn O. Pearce
2007-04-05 15:52 ` Nicolas Pitre
2007-04-05 6:54 ` Shawn O. Pearce
2007-04-05 15:34 ` Linus Torvalds
2007-04-05 15:53 ` Shawn O. Pearce
2007-04-05 16:21 ` Linus Torvalds [this message]
2007-04-05 17:14 ` Shawn O. Pearce
2007-04-05 21:17 ` Florian Weimer
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.0704050910590.6730@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=danahow@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.org \
--cc=spearce@spearce.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).