From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2009, #03; Tue, 08)
Date: Tue, 8 Dec 2009 17:20:59 +0700 [thread overview]
Message-ID: <fcaeb9bf0912080220s5a999226i944d2e3646b34d49@mail.gmail.com> (raw)
In-Reply-To: <7vmy1tg6ll.fsf@alter.siamese.dyndns.org>
On Tue, Dec 8, 2009 at 4:25 PM, Junio C Hamano > * nd/sparse
(2009-11-25) 20 commits.
> (merged to 'next' on 2009-11-25 at 71380f5)
> + tests: rename duplicate t1009
> (merged to 'next' on 2009-11-23 at f712a41)
> + sparse checkout: inhibit empty worktree
> + Add tests for sparse checkout
> + read-tree: add --no-sparse-checkout to disable sparse checkout support
> + unpack-trees(): ignore worktree check outside checkout area
> + unpack_trees(): apply $GIT_DIR/info/sparse-checkout to the final index
> + unpack-trees(): "enable" sparse checkout and load $GIT_DIR/info/sparse-checkout
> + unpack-trees.c: generalize verify_* functions
> + unpack-trees(): add CE_WT_REMOVE to remove on worktree alone
> + Introduce "sparse checkout"
> + dir.c: export excluded_1() and add_excludes_from_file_1()
> + excluded_1(): support exclude files in index
> + unpack-trees(): carry skip-worktree bit over in merged_entry()
> + Read .gitignore from index if it is skip-worktree
> + Avoid writing to buffer in add_excludes_from_file_1()
> + Teach Git to respect skip-worktree bit (writing part)
> + Teach Git to respect skip-worktree bit (reading part)
> + Introduce "skip-worktree" bit in index, teach Git to get/set this bit
> + Add test-index-version
> + update-index: refactor mark_valid() in preparation for new options
>
> There were some test glitches reported and at least one test seems to
> be broken in the sense that it is not testing what it is trying to.
> Fix-up expected.
Indeed. I'm working on it. Hopefully I'll have something in the next few days.
--
Duy
prev parent reply other threads:[~2009-12-08 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 9:25 What's cooking in git.git (Dec 2009, #03; Tue, 08) Junio C Hamano
2009-12-08 10:20 ` Nguyen Thai Ngoc Duy [this message]
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=fcaeb9bf0912080220s5a999226i944d2e3646b34d49@mail.gmail.com \
--to=pclouds@gmail.com \
--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