Re: What's cooking in git.git (Dec 2019, #01; Mon, 2)

From: Derrick Stolee <stolee@gmail.com>
Date: Dec 4, 2019, 18:53 UTC
Message-ID: <bea26b66-ac52-8f0e-9557-c958db7be628@gmail.com>
In-Reply-To: <xmqqpnh6yfrl.fsf@gitster-ct.c.googlers.com>

On 12/2/2019 9:16 AM, Junio C Hamano wrote:

Show 25 quoted lines

> * ds/sparse-cone (2019-11-22) 19 commits
>  - sparse-checkout: check for dirty status
>  - sparse-checkout: update working directory in-process for 'init'
>  - sparse-checkout: cone mode should not interact with .gitignore
>  - sparse-checkout: write using lockfile
>  - sparse-checkout: use in-process update for disable subcommand
>  - sparse-checkout: update working directory in-process
>  - sparse-checkout: sanitize for nested folders
>  - unpack-trees: add progress to clear_ce_flags()
>  - unpack-trees: hash less in cone mode
>  - sparse-checkout: init and set in cone mode
>  - sparse-checkout: use hashmaps for cone patterns
>  - sparse-checkout: add 'cone' mode
>  - trace2: add region in clear_ce_flags
>  - sparse-checkout: create 'disable' subcommand
>  - sparse-checkout: add '--stdin' option to set subcommand
>  - sparse-checkout: 'set' subcommand
>  - clone: add --sparse mode
>  - sparse-checkout: create 'init' subcommand
>  - sparse-checkout: create builtin with 'list' subcommand
> 
>  Management of sparsely checked-out working tree has gained a
>  dedicated "sparse-checkout" command.
> 
>  How well is this topic done at this point?

Hopefully this is ready to merge and I can start on the follow-up topics. I think this is ready enough that any further comments can be done in follow-up commits.

That said, I thought the topic was in that state before the 2.24.0 release, but then Szeder found several good points worthy to address here. He is CC'd to hopefully comment.

Show 16 quoted lines

> * ds/fsmonitor-testing (2019-11-22) 11 commits
>  - test-lib: clear watchman watches at test completion
>  - t7519: disable external GIT_TEST_FSMONITOR variable
>  - t7063: disable fsmonitor with status cache
>  - tests: disable fsmonitor in submodule tests
>  - t3600-rm.sh: disable fsmonitor when deleting populated submodule
>  - t3030-merge-recursive.sh: disable fsmonitor when tweaking GIT_WORK_TREE
>  - fsmonitor: disable fsmonitor with worktrees
>  - t1510-repo-setup.sh: disable fsmonitor if no .git dir
>  - t1301-shared-repo.sh: disable FSMONITOR
>  - fsmonitor: do not output to stderr for tests
>  - fsmonitor: disable in a bare repo
> 
>  Updates around testing fsmoitor integration.
> 
>  Will merge to 'next'.

Please hold off. As mentioned in the thread, I didn't do a very good job of writing my commit messages. I do plan to get back to this with better descriptions, and that may motivate others to read the series and provide feedback.

Thanks, -Stolee