git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org, Derrick Stolee <stolee@gmail.com>
Subject: Re: What's cooking in git.git (Dec 2019, #01; Mon, 2)
Date: Fri, 06 Dec 2019 13:31:35 -0800	[thread overview]
Message-ID: <xmqqd0d1w37s.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <bea26b66-ac52-8f0e-9557-c958db7be628@gmail.com> (Derrick Stolee's message of "Wed, 4 Dec 2019 13:53:10 -0500")

Derrick Stolee <stolee@gmail.com> writes:

> On 12/2/2019 9:16 AM, Junio C Hamano wrote:
>> * 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.

Ping?

  reply	other threads:[~2019-12-06 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 14:16 What's cooking in git.git (Dec 2019, #01; Mon, 2) Junio C Hamano
2019-12-02 15:59 ` Elijah Newren
2019-12-02 21:05 ` Denton Liu
2019-12-03 16:34   ` Junio C Hamano
2019-12-03 16:38   ` Junio C Hamano
2019-12-04  6:19     ` Denton Liu
2019-12-04 18:14       ` Junio C Hamano
2019-12-04 18:53 ` Derrick Stolee
2019-12-06 21:31   ` Junio C Hamano [this message]
2019-12-13 13:38 ` Ed Maste
2019-12-13 13:58   ` Ed Maste
2019-12-13 19:02     ` Junio C Hamano
2019-12-16  2:26 ` Heba Waly

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqd0d1w37s.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=stolee@gmail.com \
    --cc=szeder.dev@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).