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

Re: [PATCH v2] sparse-checkout: be consistent with end of options markers

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 26, 2023, 20:12 UTC
Message-ID
<xmqqil4khgdz.fsf@gitster.g>
In-Reply-To
<pull.1625.v2.git.git.1703619562639.gitgitgadget@gmail.com>
"Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 16 quoted lines
> Remove the erroneous PARSE_OPT_KEEP_UNKNOWN_OPT flag now to fix this
> bug.  Note that this does mean that anyone who might have been using
>
>   git sparse-checkout [add|set] [--[no-]cone] --foo --bar
>
> to request paths or patterns '--foo' and '--bar' will now have to use
>
>   git sparse-checkout [add|set] [--[no-]cone] -- --foo --bar
>
> That makes sparse-checkout more consistent with other git commands,
> provides users much friendlier error messages and behavior, and is
> consistent with the all-caps warning in git-sparse-checkout.txt that
> this command "is experimental...its behavior...will likely change".  :-)
>
> Signed-off-by: Elijah Newren <newren@gmail.com>
> ---

Let me drop jc/sparse-checkout-eoo topic and queue this instead, and then resurrect the "use default for 'set' only when !stdin" as a separate topic.

Thanks.
Previous: Elijah Newren via GitGitGadget
Message 8 of 8 in “sparse-checkout: be consistent with end of options markers”
  1. sparse-checkout: be consistent with end of options markersElijah Newren via GitGitGadget, Dec 24, 2023
  2. Jeff KingDec 24, 2023
  3. Junio C HamanoDec 26, 2023
  4. Jeff KingDec 28, 2023
  5. Junio C HamanoDec 26, 2023
  6. Elijah NewrenDec 26, 2023
  7. sparse-checkout: be consistent with end of options markersElijah Newren via GitGitGadget, Dec 26, 2023
  8. Junio C HamanoDec 26, 2023

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.