From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2008, #02; Sun, 14)
Date: Tue, 16 Dec 2008 08:35:02 +0700 [thread overview]
Message-ID: <fcaeb9bf0812151735g37f14022o8176a342f9b0d9f1@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0812151423390.19665@iabervon.org>
On 12/16/08, Daniel Barkalow <barkalow@iabervon.org> wrote:
> > + grep: skip files outside sparse checkout area
> > + Prevent diff machinery from examining worktree outside sparse
> > checkout
>
>
> I think this patch (slightly reframed) would be good to have independantly
> of the series; it also means that we won't do weird things if someone
> changes a file in the worktree which is marked as CE_VALID, and may well
> may CE_VALID sufficient for the index representation of paths outside the
> checkout.
I have made a fixup patch for CE_VALID. Unfortunately I have not had
time to write tests and finish it before submitting. I may have free
time this weekend to complete.
--
Duy
next prev parent reply other threads:[~2008-12-16 1:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 8:24 What's cooking in git.git (Dec 2008, #02; Sun, 14) Junio C Hamano
2008-12-14 10:44 ` Johannes Schindelin
2008-12-14 11:15 ` Jeff King
2008-12-14 11:24 ` Johannes Schindelin
2008-12-14 11:17 ` Jakub Narebski
2008-12-14 13:15 ` Miklos Vajna
2008-12-14 11:08 ` Jakub Narebski
2008-12-15 6:16 ` Junio C Hamano
2008-12-15 19:59 ` Daniel Barkalow
2008-12-16 1:35 ` Nguyen Thai Ngoc Duy [this message]
2008-12-16 1:42 ` Junio C Hamano
2008-12-16 3:36 ` Daniel Barkalow
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=fcaeb9bf0812151735g37f14022o8176a342f9b0d9f1@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).