From: Linus Torvalds <torvalds@osdl.org>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Seeing various mode changes on cygwin
Date: Mon, 10 Oct 2005 11:22:46 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0510101120410.14597@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0510101354520.23242@iabervon.org>
On Mon, 10 Oct 2005, Daniel Barkalow wrote:
>
> Actually, you're right; it is information about the behavior of the
> working tree, and is also needed if you want to compare the working tree
> against a tree object, in which case you aren't using the index at all.
Git _always_ uses the index for working tree operations.
It may take the actual file _data_ from the working tree, but it will take
the list of files from the index, so it's certainly possible to link the
index to the working tree.
That said, I don't think it's necessarily a good idea. You can have
temporary indexes for various operations that ignore the main one (ie any
random
GIT_INDEX_FILE=tmp git-read-tree ...
will create a new index).
So I think it's much better to have a config file.
I'll write something up. Make it extensible while at it.
Linus
next prev parent reply other threads:[~2005-10-10 18:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 18:00 Seeing various mode changes on cygwin Jonas Fonseca
2005-10-08 18:51 ` Junio C Hamano
2005-10-08 21:36 ` Alex Riesen
2005-10-08 23:36 ` Junio C Hamano
2005-10-09 2:19 ` Linus Torvalds
2005-10-09 6:46 ` Junio C Hamano
2005-10-10 6:48 ` Daniel Barkalow
2005-10-10 7:38 ` Junio C Hamano
2005-10-10 17:59 ` Daniel Barkalow
2005-10-10 18:22 ` Linus Torvalds [this message]
2005-10-10 21:35 ` Add ".git/config" file parser Linus Torvalds
2005-10-10 21:47 ` Linus Torvalds
2005-10-10 21:50 ` H. Peter Anvin
2005-10-10 22:12 ` Linus Torvalds
2005-10-12 0:25 ` Junio C Hamano
2005-10-12 7:43 ` [PATCH] Use core.filemode Junio C Hamano
2005-10-09 3:43 ` Seeing various mode changes on cygwin H. Peter Anvin
2005-10-09 13:02 ` Alex Riesen
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=Pine.LNX.4.64.0510101120410.14597@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).