From: Petr Baudis <pasky@ucw.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>,
GIT <git@vger.kernel.org>
Subject: Re: 'read-tree -m head' vs 'read-tree head'
Date: Tue, 3 May 2005 23:34:44 +0200 [thread overview]
Message-ID: <20050503213444.GD15995@pasky.ji.cz> (raw)
In-Reply-To: <7vbr7sw2aj.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Tue, May 03, 2005 at 09:13:40PM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> That said, I've been wondering if "git-read-tree -m <tree>"
> always does the same thing (but only making the operation
> afterwards faster) as "git-read-tree <tree>". That is, if there
> is a valid use case where you would want to use it without "-m"
> because "-m" does something wrong. If there is no such valid
> use case probably we should always do "-m" version if we are
> reading only one tree, practically deprecating "-m" flag to the
> same status as "-r" flag to git-diff-cache.
>
> However, I have not had time to think things through and have
> not bugged Linus about it myself.
-m fails when your cache file is missing/corrupted. Not that it cannot
be fixed, just remember to fix it if you are going to do what you
described.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-05-03 21:28 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 [this message]
2005-05-04 6:54 ` Junio C Hamano
2005-05-04 7:01 ` Thomas Glanzmann
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=20050503213444.GD15995@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=sithglan@stud.uni-erlangen.de \
/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).