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

Re: [PATCH] rebase: add `--update-refs=interactive`

From
D. Ben Knoble <ben.knoble@gmail.com>
Date
Feb 11, 2025, 19:28 UTC
Message-ID
<CALnO6CDN627+SUC6BWBvVjFnU5qKsBrfLkmX2okv8J8+wgDDRA@mail.gmail.com>
In-Reply-To
<bc0de52b59f289e1388f1581fcfa49453365e21a.camel@intelfx.name>
On Tue, Feb 11, 2025 at 6:33 AM Ivan Shapovalov <intelfx@intelfx.name> wrote:
Show 14 quoted lines
>
> On 2025-02-10 at 15:22 -0500, D. Ben Knoble wrote:
> >
> > Based on `git grep -e '--.*\[=' Documentation/git-*.txt`, I think this
> > should be more like
> >
> >     --update-refs[=interactive]::
> >     --no-update-refs::
> >
> > But maybe that unintentionally suggests that `=interactive` is the default?
>
> Perhaps --update-refs[=(yes|no|interactive)] then? Or is that too
> verbose? Anyway, I don't have a preference, I'll just do what I'm told
> here.

I don't have a strong opinion, and I think this is being discussed elsewhere in this thread.

Show 8 quoted lines
> > Should we add a test for this?
> >
>
> Any suggestions what exactly I should test here? I don't have much
> experience testing interactive CLI tools, so I'd appreciate some hints.
>
> --
> Ivan Shapovalov / intelfx /

Give t/README a glance; t3404 is probably a good place to start given "git grep update-refs t."

-- 
D. Ben Knoble
Previous: Ivan ShapovalovNext: D. Ben Knoble
Message 6 of 16 in “rebase: add `--update-refs=interactive`”
  1. rebase: add `--update-refs=interactive`Ivan Shapovalov, Feb 10, 2025
  2. D. Ben KnobleFeb 10, 2025
  3. Ivan ShapovalovFeb 11, 2025
  4. Junio C HamanoFeb 11, 2025
  5. Ivan ShapovalovFeb 11, 2025
  6. D. Ben KnobleFeb 11, 2025
  7. D. Ben KnobleFeb 11, 2025
  8. Phillip WoodFeb 11, 2025
  9. Ivan ShapovalovFeb 11, 2025
  10. Phillip WoodFeb 12, 2025
  11. Junio C HamanoFeb 12, 2025
  12. Phillip WoodFeb 13, 2025
  13. Ivan ShapovalovFeb 12, 2025
  14. phillip.wood123@gmail.comFeb 13, 2025
  15. Ivan ShapovalovFeb 13, 2025
  16. phillip.wood123@gmail.comFeb 19, 2025

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.