From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: GIT <git@vger.kernel.org>
Subject: Re: 'read-tree -m head' vs 'read-tree head'
Date: Wed, 4 May 2005 09:01:48 +0200 [thread overview]
Message-ID: <20050504070148.GF18380@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <7vr7gnpjkq.fsf@assigned-by-dhcp.cox.net>
Hello Junio,
> Normally "read-tree -m" is the preferred form from
> performance point of view, especially on a large project.
> The only case you need to use "read-tree" without -m is when
> the cache contains conflicting merge results and you want to
> start from scratch.
thanks for the bottom line. That explains why Linus uses it in his
git-pull-script.
Thomas
prev parent reply other threads:[~2005-05-04 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 12:49 'read-tree -m head' vs 'read-tree head' Thomas Glanzmann
2005-05-03 19:13 ` Junio C Hamano
2005-05-03 21:34 ` Petr Baudis
2005-05-04 6:54 ` Junio C Hamano
2005-05-04 7:01 ` Thomas Glanzmann [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=20050504070148.GF18380@cip.informatik.uni-erlangen.de \
--to=sithglan@stud.uni-erlangen.de \
--cc=git@vger.kernel.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).