On Thu, 30 Nov 2006, Theodore Tso wrote:Hey, it was originally called "cache". I don't care _what_ it's called, I just want people knowing about it, because hiding it will just cripple git (ie at the very least, when you hit a merge conflict, you really do want to to understand it if you ever want to go the the "next level"). If people are more comfortable just calling it the "staging area", and talking about it in those terms, I'll be happy. Yes. And even "git diff" isn't really a problem once you understand the staging area. If people feel worried, let them use "git diff HEAD". You won't need to use git for _that_ long until you realize that since the staging area is going to match the HEAD under normal circumstances (and when it doesn't, you actually tend to prefer to get the diff against the staging area _anyway_), you'll find people just starting to use "git diff" and not worry about it. Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| David Miller | Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers. |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Linus Torvalds | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
