From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.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: Wed, 20 Nov 2019 12:02:16 +0900 [thread overview]
Message-ID: <xmqqzhgrcksn.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20191119175850.GL23183@szeder.dev> ("SZEDER Gábor"'s message of "Tue, 19 Nov 2019 18:58:50 +0100")
SZEDER Gábor <szeder.dev@gmail.com> writes:
> 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:
Ah, this is also just 2/2 of a two-patch pair; I guess I was extra
sloppy on that day.
It seems that 1/2 was also incomplete, so let me discard this and
expect both of them to resurface later.
>> * 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:
OK. I had an impression that it was something relatively easily
patched to restore the plumbing behaviour without taking the
remainder of the series with a follow-on work. If it is not the
case, perhaps I should revert the merge to 'next' and kick it back
to 'pu'.
Thanks for stopping me.
next prev parent reply other threads:[~2019-11-20 3:02 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
2019-11-20 3:02 ` Junio C Hamano [this message]
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
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=xmqqzhgrcksn.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.com \
--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).