git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Derrick Stolee <stolee@gmail.com>,
	Phillip Wood <phillip.wood123@gmail.com>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2019, #03; Tue, 19)
Date: Tue, 19 Nov 2019 18:58:50 +0100	[thread overview]
Message-ID: <20191119175850.GL23183@szeder.dev> (raw)
In-Reply-To: <xmqqftikxs4z.fsf@gitster-ct.c.googlers.com>

On Tue, Nov 19, 2019 at 04:05:48PM +0900, Junio C Hamano wrote:
> * ds/commit-graph-delay-gen-progress (2019-11-07) 1 commit
>   (merged to 'next' on 2019-11-19 at afa7c921be)
>  + commit-graph: use start_delayed_progress()

This commit is incomplete:

  https://public-inbox.org/git/20191111142739.GL4348@szeder.dev/

>  One kind of progress messages were always given during commit-graph
>  generation, instead of following the "if it takes more than two
>  seconds, show progress" pattern, which has been corrected.
> 
>  Will merge to 'master'.


> * ds/sparse-cone (2019-10-23) 17 commits
>   (merged to 'next' on 2019-11-19 at 1eb4b3a012)
>  + sparse-checkout: cone mode should not interact with .gitignore
>  + sparse-checkout: write using lockfile
>  + sparse-checkout: update working directory in-process
>  + sparse-checkout: sanitize for nested folders
>  + read-tree: show progress by default

This commit changed the default behaviour of a plumbing command, and
the resulting discussion concluded that such a change is not
desirable:

  https://public-inbox.org/git/6c6b9838-af7b-7212-199f-a0a3f3f2ac77@gmail.com/

>  + 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.
> 
>  Will merge to 'master'.

  parent reply	other threads:[~2019-11-19 17:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19  7:05 What's cooking in git.git (Nov 2019, #03; Tue, 19) Junio C Hamano
2019-11-19  9:38 ` Danh Doan
2019-11-20  2:52   ` Junio C Hamano
2019-11-19 17:58 ` SZEDER Gábor [this message]
2019-11-20  3:02   ` Junio C Hamano
2019-11-20 13:58     ` Derrick Stolee
2019-11-21  0:36       ` Junio C Hamano
2019-11-21 11:10         ` Derrick Stolee
2019-11-22  5:42           ` Junio C Hamano
2019-11-19 18:01 ` ag/sequencer-todo-updates , was " Alban Gruin
2019-11-19 20:41   ` Jonathan Tan
2019-11-20  3:03     ` Junio C Hamano
2019-11-21  8:17       ` Alban Gruin
2019-11-23  0:47     ` Alban Gruin
2019-11-20 23:32 ` Denton Liu
2019-11-21  0:39   ` Junio C Hamano
2019-11-23 20:35 ` Philippe Blain

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=20191119175850.GL23183@szeder.dev \
    --to=szeder.dev@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=phillip.wood123@gmail.com \
    --cc=stolee@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.
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).