git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
	Markus Klinik <markus.klinik@gmx.de>,
	git@vger.kernel.org
Subject: Re: git-cvsexportcommit fails for huge commits
Date: Fri, 14 Dec 2007 14:47:03 +0100	[thread overview]
Message-ID: <200712141447.05039.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20071214091546.GA20907@coredump.intra.peff.net>

fredag 14 december 2007 skrev Jeff King:
> On Thu, Dec 13, 2007 at 11:45:54PM -0500, Jeff King wrote:
> 
> > So it seems that we could probably go with something more like 64K, and
> > then only truly pathological cases should trigger the behavior.
> 
> So here is a cleaned up patch. It bumps the maximum size to 64kB, adds
> scalar support (nobody uses it, but it makes sense for the interface to
> match that of safe_pipe_capture -- I am even tempted to just replace
> safe_pipe_capture entirely and convert the few other callers), and
> cleans up the unused safe_pipe_capture_blob.

Wouldn't using the POSIX::ARG_MAX constant work?

-- robin

  reply	other threads:[~2007-12-14 13:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 20:04 git-cvsexportcommit fails for huge commits Markus Klinik
2007-12-12  8:31 ` Jeff King
2007-12-12  9:21   ` Junio C Hamano
2007-12-12  9:25     ` Jeff King
2007-12-14  3:22       ` Junio C Hamano
2007-12-14  4:45         ` Jeff King
2007-12-14  9:15           ` Jeff King
2007-12-14 13:47             ` Robin Rosenberg [this message]
2007-12-15 10:09               ` Jeff King
2007-12-12 16:02   ` Linus Torvalds
2007-12-12 16:17     ` Jeff King
2007-12-12 19:58   ` Martin Langhoff
2007-12-13  4:17     ` Jeff King
2007-12-13  8:39       ` Markus Klinik
2007-12-13  9:01         ` 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=200712141447.05039.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=markus.klinik@gmx.de \
    --cc=peff@peff.net \
    /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).