Trying again from plain old gmail which I think does not send a multipart content.
On Fri, Nov 7, 2014 at 11:06 PM, Martin von Zweigbergk <martinv...@gmail.com> wrote: > Is this also related to "git checkout $rev ." not removing removed files? > What you say about the difference in implementation between checkout and > reset sounds vaguely familiar from when I looked at it some years ago. > Curiously, I just talked to Jonathan about this over lunch yesterday. I > think we would both be happy to get that oddity of checkout fixed. If what > you mention here is indeed related to fixing that, it does complicate things > with regards to backwards compatibility. > > > On Fri Nov 07 2014 at 11:24:09 AM Jeff King <p...@peff.net> wrote: >> >> On Fri, Nov 07, 2014 at 09:14:42AM -0800, Junio C Hamano wrote: >> >> > Jeff King <p...@peff.net> writes: >> > >> > > Is there a reason that we don't use this diff technique for checkout? >> > >> > I suspect that the reasons are probably mixture of these: >> > >> > (1) the code path may descend from checkout-index and predates the >> > in-core diff machinery; >> > >> > (2) in the context of checkout-index, it was more desirable to be >> > able to say "I want the contents on the filesystem, even if you >> > think I already have it there, as you as a new software are >> > likely to be wrong and I know better"; or >> > >> > (3) it was easier to code that way ;-) >> > >> > I do not see there is any reason not to do what you suggest. >> >> OK. It's not very much code (and can mostly be lifted from git-reset), >> so I may take a stab at it. >> >> -Peff >> -- >> To unsubscribe from this list: send the line "unsubscribe git" in >> the body of a message to majord...@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
