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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 11, 2025, 16:50 UTC
Message-ID
<xmqqfrkk1l4i.fsf@gitster.g>
In-Reply-To
<bc0de52b59f289e1388f1581fcfa49453365e21a.camel@intelfx.name>
Ivan Shapovalov <intelfx@intelfx.name> writes:
Show 14 quoted lines
>> >  --update-refs::
>> >  --no-update-refs::
>> > +--update-refs=interactive::
>> 
>> 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?

If `--update-refs` does take values that the git_parse_maybe_bool() helper parses as a Boolean value, I do not think the above is verbose at all. Rather, it is a disservice to the users if the documentation does not mention yes/no in such a case. I'd say listing other Boolean synonyms like yes/true/on/no/false/off is too verbose, though ;-).

> Anyway, I don't have a preference, I'll just do what I'm told
That is not quite in line with how we'd like to operate.

It is your itch. Others may give suggestions to help you polish it, but ultimately, we would not want to accept a patch that the author does not agree with.

Thanks.
Previous: Ivan ShapovalovNext: Ivan Shapovalov
Message 4 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.