git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2021, #02; Wed, 8)
Date: Thu, 9 Sep 2021 07:12:54 -0700	[thread overview]
Message-ID: <CABPp-BGW4Bfjgi580mXwtQMQt=PLpgGsEWg6fNw41VRj1B3LUg@mail.gmail.com> (raw)
In-Reply-To: <xmqqsfyf5b74.fsf@gitster.g>

A few comments on some topics from other folks...

On Wed, Sep 8, 2021 at 8:40 AM Junio C Hamano <gitster@pobox.com> wrote:

> * pb/test-use-user-env (2021-09-07) 3 commits
>  - test-lib-functions: keep user's debugger config files and TERM in 'debug'
>  - test-lib-functions: optionally keep HOME, TERM and SHELL in 'test_pause'
>  - test-lib-functions: use 'TEST_SHELL_PATH' in 'test_pause'
>
>  Teach test_pause and test_debug to allow using the HOME and TERM
>  environment variables the user usually uses.
>
>  Will merge to 'next'?

Sounds good to me; I'm happy with the latest series.

> * js/retire-preserve-merges (2021-09-07) 11 commits
>  - sequencer: restrict scope of a formerly public function
>  - rebase: remove a no-longer-used function
>  - rebase: stop mentioning the -p option in comments
>  - rebase: remove obsolete code comment
>  - rebase: drop the internal `rebase--interactive` command
>  - git-svn: drop support for `--preserve-merges`
>  - rebase: drop support for `--preserve-merges`
>  - pull: remove support for `--rebase=preserve`
>  - tests: stop testing `git rebase --preserve-merges`
>  - remote: warn about unhandled branch.<name>.rebase values
>  - t5520: do not use `pull.rebase=preserve`
>
>  The "--preserve-merges" option of "git rebase" has been removed.
>
>  Will merge to 'next'?

I came a bit late to the party, but skimmed over the series as well.
I'm very happy with the cleanups.  The direction of the patches looks
good in general, and didn't spot any problems in my spot checking.
Merging down sounds good to me.

> * ds/sparse-index-ignored-files (2021-09-07) 10 commits
>  - sparse-checkout: clear tracked sparse dirs
>  - sparse-index: add SPARSE_INDEX_MEMORY_ONLY flag
>  - attr: be careful about sparse directories
>  - sparse-checkout: create helper methods
>  - sparse-index: use WRITE_TREE_MISSING_OK
>  - sparse-index: silently return when cache tree fails
>  - unpack-trees: fix nested sparse-dir search
>  - sparse-index: silently return when not using cone-mode patterns
>  - t7519: rewrite sparse index test
>  - Merge branch 'ds/add-with-sparse-index' into ds/sparse-index-ignored-files
>  (this branch is used by sg/test-split-index-fix.)
>
>  In cone mode, the sparse-index codepath learned to remove ignored
>  files (like build artifacts) outside the sparse cone, allowing the
>  entire directory outside the sparse cone to be removed, which is
>  especially useful when the sparse patterns change.
>
>  Will merge to 'next'?

I've reviewed each of the rounds in detail and I'm happy with this
one; I think it's ready.

      parent reply	other threads:[~2021-09-09 14:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 15:38 What's cooking in git.git (Sep 2021, #02; Wed, 8) Junio C Hamano
2021-09-08 16:24 ` Taylor Blau
2021-09-08 19:23   ` Junio C Hamano
2021-09-09  1:02     ` Taylor Blau
2021-09-08 21:27   ` Jeff King
2021-09-08 16:55 ` Azeem Bande-Ali
2021-09-08 19:20   ` Junio C Hamano
2021-09-08 17:50 ` Philippe Blain
2021-09-08 21:57 ` Derrick Stolee
2021-09-09 14:23   ` Elijah Newren
2021-09-09  2:59 ` Ramsay Jones
2021-09-09 17:45   ` Junio C Hamano
2021-09-09 11:03 ` js/scalar, was " Johannes Schindelin
2021-09-10  8:52   ` Junio C Hamano
2021-09-09 11:05 ` rs/range-diff-avoid-segfault-with-I, " Johannes Schindelin
2021-09-09 11:08 ` js/retire-preserve-merges, " Johannes Schindelin
2021-09-10  5:00   ` Junio C Hamano
2021-09-09 11:08 ` mr/bisect-in-c-4, " Johannes Schindelin
2021-09-10  5:07   ` Junio C Hamano
2021-09-10  9:33     ` Johannes Schindelin
2021-09-09 11:13 ` lh/systemd-timers, " Johannes Schindelin
2021-09-09 11:15 ` ar/submodule-add-more, " Johannes Schindelin
2021-09-10  5:30   ` Junio C Hamano
2021-09-09 11:18 ` Ævar Arnfjörð Bjarmason
2021-09-09 14:12 ` Elijah Newren [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

  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='CABPp-BGW4Bfjgi580mXwtQMQt=PLpgGsEWg6fNw41VRj1B3LUg@mail.gmail.com' \
    --to=newren@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.
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).