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>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: en/removing-untracked-fixes [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)]
Date: Thu, 30 Sep 2021 23:20:02 -0700	[thread overview]
Message-ID: <CABPp-BHKOt+x+B3DGh3BJV_voP64pvTrL5B-w4hWqHNKfr2K3w@mail.gmail.com> (raw)
In-Reply-To: <xmqqh7e18soj.fsf@gitster.g>

On Thu, Sep 30, 2021 at 6:09 PM Junio C Hamano <gitster@pobox.com> wrote:

> * en/removing-untracked-fixes (2021-09-27) 12 commits
>  - Documentation: call out commands that nuke untracked files/directories
>  - Comment important codepaths regarding nuking untracked files/dirs
>  - unpack-trees: avoid nuking untracked dir in way of locally deleted file
>  - unpack-trees: avoid nuking untracked dir in way of unmerged file
>  - Change unpack_trees' 'reset' flag into an enum
>  - Remove ignored files by default when they are in the way
>  - unpack-trees: make dir an internal-only struct
>  - unpack-trees: introduce preserve_ignored to unpack_trees_options
>  - read-tree, merge-recursive: overwrite ignored files by default
>  - checkout, read-tree: fix leak of unpack_trees_options.dir
>  - t2500: add various tests for nuking untracked files
>  - Merge branch 'en/am-abort-fix' into en/removing-untracked-fixes
>
>  Various fixes in code paths that move untracked files away to make room.
>
>  Will merge to 'next'?

Phillip (Wood) just recently acked the series[1].

Ævar made multiple good suggestions on an earlier round that I
incorporated.  A few others commented as well and I incorporated each
or responded why it didn't make sense, I believe to the individuals'
satisfaction.

However, on the latest series, Ævar has tried to suggest some changes
around the 'dir' member that he seems to want to see squashed in.
There's multiple reasons I don't like those changes, and even if we
ended up adopting them, I think they'd need a separate commit with a
good explanation of the assumptions being added by those changes[2].
I think such a change, if others want it, could and likely should be
submitted separately from this series.  And I suspect he's struggling
just as hard to see my point of view as I am to see his.

So...maybe I reroll the series with Phillip's Acked-by, and give it a
few days to see if either Ævar or I can convince the other?

[1] https://lore.kernel.org/git/b23bb983-39e6-75ad-0cb5-d9a5ba2cd4d8@gmail.com/
[2] https://lore.kernel.org/git/CABPp-BGi03JunRaMF_8SJKC00byOnq1kL3JyYhKWatz8-B4RsA@mail.gmail.com/

  reply	other threads:[~2021-10-01  6:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  1:01 What's cooking in git.git (Sep 2021, #09; Thu, 30) Junio C Hamano
2021-10-01  6:20 ` Elijah Newren [this message]
2021-10-01  8:51   ` en/removing-untracked-fixes [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Ævar Arnfjörð Bjarmason
2021-10-01 17:05   ` en/removing-untracked-fixes [ Junio C Hamano
2021-10-01  6:31 ` en/remerge-diff [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Elijah Newren
2021-10-01  7:01   ` Jeff King
2021-10-01 12:05 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Ævar Arnfjörð Bjarmason
2021-10-01 12:08 ` ab/fsck-unexpected-type Ævar Arnfjörð Bjarmason
2021-10-01 14:32 ` ab/parse-options-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:35 ` ab/sanitize-leak-ci & more leak fixes soon-or-not Ævar Arnfjörð Bjarmason
2021-10-01 14:48 ` ab/refs-errno-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:56 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Jeff Hostetler
2021-10-01 15:01 ` ab/align-parse-options-help & ab/help-config-vars Ævar Arnfjörð Bjarmason
2021-10-01 15:05 ` ab/lib-subtest Ævar Arnfjörð Bjarmason
2021-10-01 15:07 ` ab/config-based-hooks-1 Ævar Arnfjörð Bjarmason

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-BHKOt+x+B3DGh3BJV_voP64pvTrL5B-w4hWqHNKfr2K3w@mail.gmail.com \
    --to=newren@gmail.com \
    --cc=avarab@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).