From: Shawn Pearce <spearce@spearce.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Avoid accessing a slow working copy during diffcore operations.
Date: Fri, 15 Dec 2006 10:05:00 -0500 [thread overview]
Message-ID: <20061215150500.GC17860@spearce.org> (raw)
In-Reply-To: <eltr9v$b4q$1@sea.gmane.org>
Jakub Narebski <jnareb@gmail.com> wrote:
> Shawn O. Pearce wrote:
>
> > +# Define NO_FAST_WORKING_DIRECTORY if accessing objects in pack files is
> > +# generally faster on your platform than accessing the working directory.
> > +#
>
> Hmmm... I wonder if generated by autoconf ./configure script can autodetect
> that. Probably not.
I think it would be difficult to perform an automatic performance
test prior to building Git to determine how we should build Git on
the current platform. Besides, Cygwin users tend to not use the
./configure script as it takes longer than just using the Makefile.
AFAIK the only "OS" which suffers from this problem is Windows.
Anything else that Git has been ported too has reasonably fast
syscalls for file IO, which means this should be unset.
--
next prev parent reply other threads:[~2006-12-15 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 11:15 [PATCH] Avoid accessing a slow working copy during diffcore operations Shawn O. Pearce
2006-12-14 13:57 ` Alex Riesen
2006-12-14 14:12 ` Johannes Schindelin
2006-12-14 14:49 ` Alex Riesen
2006-12-14 15:37 ` Johannes Schindelin
2006-12-15 9:55 ` Jakub Narebski
2006-12-15 15:05 ` Shawn Pearce [this message]
2006-12-16 6:03 ` Junio C Hamano
2006-12-16 11:54 ` Johannes Schindelin
2006-12-16 13:38 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061215150500.GC17860@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jnareb@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).