From: Elijah Newren <newren@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Taylor Blau <me@ttaylorr.com>,
Derrick Stolee <dstolee@microsoft.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: en/keep-cwd (Was: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3))
Date: Tue, 7 Dec 2021 12:33:59 -0800 [thread overview]
Message-ID: <CABPp-BHhtZzq3rqbaHm62LOkA6cnzRC6cKokGP7s2ZsQzqjJrw@mail.gmail.com> (raw)
In-Reply-To: <211207.86ee6opy0f.gmgdl@evledraar.gmail.com>
On Tue, Dec 7, 2021 at 1:25 AM Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>
> On Mon, Dec 06 2021, Elijah Newren wrote:
>
> > On Mon, Dec 6, 2021 at 5:57 PM Junio C Hamano <gitster@pobox.com> wrote:
> >>
> >> * en/keep-cwd (2021-12-01) 11 commits
> >> - t2501: simplify the tests since we can now assume desired behavior
> >> - dir: new flag to remove_dir_recurse() to spare the original_cwd
> >> - dir: avoid incidentally removing the original_cwd in remove_path()
> >> - stash: do not attempt to remove startup_info->original_cwd
> >> - rebase: do not attempt to remove startup_info->original_cwd
> >> - clean: do not attempt to remove startup_info->original_cwd
> >> - symlinks: do not include startup_info->original_cwd in dir removal
> >> - unpack-trees: add special cwd handling
> >> - unpack-trees: refuse to remove startup_info->original_cwd
> >> - setup: introduce startup_info->original_cwd
> >> - t2501: add various tests for removing the current working directory
> >>
> >> Many git commands that deal with working tree files try to remove a
> >> directory that becomes empty (i.e. "git switch" from a branch that
> >> has the directory to another branch that does not would attempt
> >> remove all files in the directory and the directory itself). This
> >> drops users into an unfamiliar situation if the command was run in
> >> a subdirectory that becomes subject to removal due to the command.
> >> The commands have been taught to keep an empty directory if it is
> >> the directory they were started in to avoid surprising users.
> >
> > Very nicely written summary.
> >
> >>
> >> Needs review.
> >> There are some comments on earlier rounds; the latest one needs a
> >> serious review or at least Acks from past commentors.
> >> source: <pull.1140.v5.git.git.1638340854.gitgitgadget@gmail.com>
> >
> > If it helps, there are two parts to the review:
> > - Do we want this feature?
> > - Does this patch series implement the feature correctly?
...
> So I've got no objections to these changes going in as they stand.
Thanks.
> If
> anyone is interested in pulling at the "let's not make it die" thread
> that can always be done later, or we can make it configurable or
> whatever.
>
> I don't think this needs to be part of your initial series, but just a
> question:
>
> Isn't a logical follow-up after it to change the various things like
> "git bisect that refuse to run in subdirectories to happily do so?
> I.e. the reason for those is specifically this "cwd goes away". Both
> because of our bad handling of it, and due to any user confusion that'll
> be addressed by that cwd sticking around".
Both sound like potentially relevant logical follow-ups.
next prev parent reply other threads:[~2021-12-07 20:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 1:37 What's cooking in git.git (Dec 2021, #01; Fri, 3) Junio C Hamano
2021-12-06 19:13 ` Phillip Wood
2021-12-06 19:24 ` Junio C Hamano
2021-12-08 12:42 ` Johannes Schindelin
2021-12-09 1:02 ` Junio C Hamano
2021-12-09 10:39 ` Phillip Wood
2021-12-07 6:00 ` en/keep-cwd (Was: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3)) Elijah Newren
2021-12-07 9:17 ` Ævar Arnfjörð Bjarmason
2021-12-07 20:33 ` Elijah Newren [this message]
2021-12-07 18:26 ` en/keep-cwd Junio C Hamano
2021-12-08 12:46 ` en/keep-cwd (Was: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3)) Johannes Schindelin
2021-12-07 15:54 ` What's cooking in git.git (Dec 2021, #01; Fri, 3) Derrick Stolee
2021-12-07 19:37 ` cf/fetch-set-upstream-while-detached (was: What's cooking in git.git (Dec 2021, #01; Fri, 3)) Ævar Arnfjörð Bjarmason
2021-12-07 20:41 ` cf/fetch-set-upstream-while-detached Junio C Hamano
2021-12-07 22:04 ` [PATCH v5] pull, fetch: fix segfault in --set-upstream option Æ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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABPp-BHhtZzq3rqbaHm62LOkA6cnzRC6cKokGP7s2ZsQzqjJrw@mail.gmail.com \
--to=newren@gmail.com \
--cc=avarab@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
--cc=phillip.wood123@gmail.com \
--cc=sunshine@sunshineco.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).