From: Junio C Hamano Date: Wed, 01 Feb 2006 02:31:58 GMT Subject: Re: [Census] So who uses git? Message-ID: <7v64nzollt.fsf@assigned-by-dhcp.cox.net> In-Reply-To: Linus Torvalds writes: > They're fast, because they are purely in the cache (well, git-update-index > obviously isn't, but the new op wouldn't be any _slower_ than the old > one). > > Looks simple enough. The big thing to remember is to clear that > "implicitly up-to-date" flag whenever we make changes (ie we'd probably > make "add_cache_entry()" always clear it, possibly with a flag to add it > as "pre-verified" which would set it). > > Comments? Junio, what do you think? Somehow this reminds me of a "feature" we added quite a long time ago to support "update-index without working tree". I think this should work fine as a mechanism, but I am a bit worried about the convenience and safety aspect. It _might_ make sense to do what RCS does; check out read-only copy by default and set the "assume unchanged" flag, to prevent people from accidentally modifying the working tree copy without telling the index about it.