From: Yasushi SHOJI <yashi@atmark-techno.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: gitweb - option to disable rename detection
Date: Wed, 17 Aug 2005 08:14:23 +0900 [thread overview]
Message-ID: <871x4txynk.wl@mail2.atmark-techno.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0508151542290.3553@g5.osdl.org>
At Mon, 15 Aug 2005 15:43:26 -0700 (PDT),
Linus Torvalds wrote:
>
> On Tue, 16 Aug 2005, Yasushi SHOJI wrote:
> >
> > > Instead of disabling it entirely, how about just having some limit on it?
> >
> > ah, that's a good idea. here is a quick and dirty patch.
>
> This makes it somewhat more expensive.
yes. but much cheaper than OOM ;P
> - I was thinking about disabling it
> in git-diff-tree, since the rename logic already knows how many
> new/deleted files there are.
I'll leave this feature for homework. I'll work on
prepare_temp_file() first since it seems to fix my problem.
regards,
--
yashi
prev parent reply other threads:[~2005-08-16 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 18:31 gitweb - option to disable rename detection Yasushi SHOJI
2005-08-15 18:53 ` Linus Torvalds
2005-08-15 20:48 ` Yasushi SHOJI
2005-08-15 22:43 ` Linus Torvalds
2005-08-16 1:21 ` Junio C Hamano
2005-08-16 23:14 ` Yasushi SHOJI [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=871x4txynk.wl@mail2.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).