From: Nicolas Pitre <nico@cam.org>
To: Dana How <danahow@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH 09/13] drop objects larger than --blob-limit if specified
Date: Fri, 06 Apr 2007 16:12:57 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0704061604160.28181@xanadu.home> (raw)
In-Reply-To: <56b7f5510704061109n2878a221p391b7c3edba89c63@mail.gmail.com>
On Fri, 6 Apr 2007, Dana How wrote:
> * Avoiding (e.g.) 2GB+ files when none already exist in the repository --
> either the filesystem doesn't support anything beyond the limit,
> or we don't want to use a >31b off_t with mmap. (Perhaps
> the latter case is completely avoided by some glibc 64b trickery,
> but is that always true?) Only the write rollback approach can address this.
If the filesystem doesn't support anything beyond the limit, you cannot
perform any rollback either. Because if you roll back that's because
you crossed the limit already. But you're not supposed to even be able
to cross that limit in the first place if the filesystem is limited.
Nicolas
prev parent reply other threads:[~2007-04-06 20:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 22:36 [PATCH 09/13] drop objects larger than --blob-limit if specified Dana How
[not found] ` <al pine.LFD.0.98.0704052103410.28181@xanadu.home>
[not found] ` <56b7f5510704051919v7daac590m 6ac52c4fcabd5321@mail.gmail.com>
2007-04-06 1:04 ` Nicolas Pitre
2007-04-06 2:19 ` Dana How
2007-04-06 3:20 ` Nicolas Pitre
2007-04-06 15:49 ` Linus Torvalds
[not found] ` <56b7f55 10704061109n2878a221p391b7c3edba89c63@mail.gmail.com>
2007-04-06 18:09 ` Dana How
2007-04-06 19:21 ` Nicolas Pitre
2007-04-06 19:24 ` Linus Torvalds
2007-04-06 22:33 ` Junio C Hamano
2007-04-08 1:53 ` David Lang
2007-04-06 20:12 ` Nicolas Pitre [this message]
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=alpine.LFD.0.98.0704061604160.28181@xanadu.home \
--to=nico@cam.org \
--cc=danahow@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@linux-foundation.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).