git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] rebase, cherry-pick, revert: only run from toplevel

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 1, 2021, 05:29 UTC
Message-ID
<xmqqk0k0sw2h.fsf@gitster.g>
In-Reply-To
<CABPp-BFmU+RaAjq4_0-PSfRgH1Jc63nN0fMuDWk2+iDbdz7CCA@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
Show 6 quoted lines
> Ooh, this sounds intriguing to me...but what if we changed that rule
> slightly and just decided to never make the cwd go away?  Currently,
> the checkout code removes directories if they have no tracked or
> untracked or ignored files left, i.e. if they're empty.  What if we
> decide to only have remove_scheduled_dirs() remove directories that
> are empty AND they are not the current working directory?

Is that generally doable? What would we do when the directory the subcommand was started from (or one of its parent directories) is not just missing but has to be a file in the revision the subcommand is trying to checkout?

Previous: Elijah NewrenNext: Elijah Newren
Message 10 of 12 in “rebase, cherry-pick, revert: only run from toplevel”
  1. rebase, cherry-pick, revert: only run from toplevelElijah Newren via GitGitGadget, Aug 31, 2021
  2. Elijah NewrenAug 31, 2021
  3. Johannes SixtAug 31, 2021
  4. Jeff KingAug 31, 2021
  5. Elijah NewrenAug 31, 2021
  6. Taylor BlauSep 1, 2021
  7. Elijah NewrenSep 1, 2021
  8. Taylor BlauSep 1, 2021
  9. Elijah NewrenSep 1, 2021
  10. Junio C HamanoSep 1, 2021
  11. Elijah NewrenSep 1, 2021
  12. Jeff KingSep 1, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.