Re: [PATCH 9/9] Build in checkout
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Feb 5, 2008, 22:45 UTC
- Message-ID
- <alpine.LSU.1.00.0802052244160.8543@racer.site>
- In-Reply-To
- <alpine.LNX.1.00.0802051716220.13593@iabervon.org>
Hi,
On Tue, 5 Feb 2008, Daniel Barkalow wrote:
Show 14 quoted lines
> On Tue, 5 Feb 2008, Johannes Schindelin wrote: > > > I suggested that: to prevent the index from needing an update. > > > > This is quite important if you have a large working tree, and switch > > branches from A to B. For example, "make" will punish you where it > > hurts. > > This isn't used for switching branches; this is used for checking out > paths. If you do "git checkout <not-head> -- <every single path>", make > will punish you, but why would you do that? I'd guess that people are > unlikely to have a significant number of non-changes in this piece of > code, just because they wouldn't list things that they didn't think had > changes.
For convenience, you can also say
$ git checkout -- <path>
and expect checkout to not really touch the unchanged files.
Ciao, Dscho