From: Krzysztof Halasa <khc@pm.waw.pl>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Paul Mackerras <paulus@samba.org>, git@vger.kernel.org
Subject: Re: Version of dirdiff to display diffs between git trees
Date: Fri, 06 May 2005 20:53:10 +0200 [thread overview]
Message-ID: <m3d5s4jieh.fsf@defiant.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0505060916320.2233@ppc970.osdl.org> (Linus Torvalds's message of "Fri, 6 May 2005 09:19:02 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> cat .git/ORIG_HEAD > .git/HEAD
> git-read-tree -m HEAD
> git-checkout-cache -f -a
> git-update-cache --refresh
>
> and you're back to your original head (the above is basically "unpull").
So, is "git-read-tree -m HEAD" actually equivalent to "git-read-tree HEAD"
and does it simply write complete index (ignoring the old one)
corresponding to given HEAD?
--
Krzysztof Halasa
next prev parent reply other threads:[~2005-05-06 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 13:18 Version of dirdiff to display diffs between git trees Paul Mackerras
2005-05-06 16:19 ` Linus Torvalds
2005-05-06 18:53 ` Krzysztof Halasa [this message]
2005-05-06 19:07 ` Linus Torvalds
2005-05-07 0:01 ` Paul Mackerras
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=m3d5s4jieh.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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