From: Shawn Pearce <spearce@spearce.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: win2k/cygwin cannot handle even moderately sized packs
Date: Tue, 7 Nov 2006 13:56:48 -0500 [thread overview]
Message-ID: <20061107185648.GE26591@spearce.org> (raw)
In-Reply-To: <20061107182636.GD26591@spearce.org>
Shawn Pearce <spearce@spearce.org> wrote:
> Shawn Pearce <spearce@spearce.org> wrote:
> > Alex Riesen <raa.lkml@gmail.com> wrote:
> > > >The patches are on the mailing list archives somewhere around
> > > >Sept. 5th timeframe from me; as I recall we dropped them as they
> > > >didn't apply on top of Junio's 64 bit index changes (which were
> > > >reverted out of next anyway).
> > >
> > > I seem to be unable to find them. Does anyone still has the
> > > patches/branch please? Junio, you did sound interested?
> > > (God, I wish I have paid attention then...)
>
> You can't find them because I never sent them. *sigh*
>
> Too f'ing bad this .patch I created with format-patch doesn't say
> what commits it was based on, 'cause I can't find anything it will
> apply too. Or better, too f'ing bad I deleted that branch. *sigh*
This thread has now proven without any shadow of a doubt that I can
be an idiot sometimes.
In this case my patch didn't apply because it was 3rd in a series;
I had two of those patches but lacked the third (a simple cleanup
patch). Redoing that simple cleanup let everything apply.
I've pushed the changes out to repo.or.cz:
http://repo.or.cz/w/git/fastimport.git
in the window-mapping branch. Note that this is based on a slightly
older version of Git (v1.4.2). There are two "tuneables" on line 376
of sha1_file.c, this is the maximum amount of memory (in bytes) to
denote to packs and the maximum chunk size of each pack (in bytes).
I planned on making these configuration options but didn't get to
that yet.
--
next prev parent reply other threads:[~2006-11-07 18:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 11:02 win2k/cygwin cannot handle even moderately sized packs Alex Riesen
2006-11-07 12:17 ` Noel Grandin
2006-11-07 13:55 ` Alex Riesen
2006-11-07 15:50 ` Jakub Narebski
2006-11-07 17:28 ` Alex Riesen
2006-11-07 17:48 ` Shawn Pearce
2006-11-07 18:13 ` Alex Riesen
2006-11-07 18:18 ` Shawn Pearce
2006-11-07 18:26 ` Shawn Pearce
2006-11-07 18:56 ` Shawn Pearce [this message]
2006-11-07 23:11 ` Alex Riesen
2006-11-08 5:19 ` Shawn Pearce
2006-11-08 13:37 ` Alex Riesen
2006-11-08 17:11 ` Shawn Pearce
2006-11-08 21:33 ` Alex Riesen
2006-11-08 22:28 ` Shawn Pearce
2006-11-07 19:27 ` Alex Riesen
2006-11-08 19:22 ` Christopher Faylor
2006-11-13 12:45 ` Johannes Schindelin
2006-11-13 17:34 ` Alex Riesen
2006-11-13 17:36 ` Alex Riesen
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=20061107185648.GE26591@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.net \
--cc=raa.lkml@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.