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

Re: [PATCH] branch: move multiple branches in a single --force

From
ASAndrea Stacchiotti <andreastacchiotti@gmail.com>
Date
Jun 12, 2025, 00:19 UTC
Message-ID
<CAEgWtF9MRbRASg1Jb3n6Ggvh8viZOpyev+OyX5DSpWQ7bMF8dg@mail.gmail.com>
In-Reply-To
<xmqqecvqjo46.fsf@gitster.g>

So, if I may ask, is the proposed patch as written (branch -f A B C X) acceptable and you just need me to rewrite the commit message or are you not interested in it at all?

Il giorno mer 11 giu 2025 alle ore 17:26 Junio C Hamano <gitster@pobox.com> ha scritto:

Show 26 quoted lines
>
> Andrea Stacchiotti <andreastacchiotti@gmail.com> writes:
>
> > Il giorno mer 11 giu 2025 alle ore 02:22 Junio C Hamano
> > <gitster@pobox.com> ha scritto:
> >>
> >> Andrea Stacchiotti <andreastacchiotti@gmail.com> writes:
> >>
> >> > This patch aims to make repointing multiple branches to the same commit-ish
> >> > easier, currently it needs a shell loop.
> >>
> >> Or "update-ref --stdin"?
> >
> > I learned something new, but I'd still like to keep advocating for a syntax
> > like `branch --some-flag A B C X` instead of feeding by hand
> > update-ref commands.
>
> I am personally not interested in such a mode, I do not know why you
> think "--some-flag" is needed when the command can figure out from
> the number of things on the command line being more than 2 just
> fine.
>
> But my comment was targetted against "it needs a shell loop" in the
> justification in the proposed log message, which is not quite
> correct.
>
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 10 in “branch: move multiple branches in a single --force”
  1. branch: move multiple branches in a single --forceAndrea Stacchiotti via GitGitGadget, Jun 10, 2025
  2. Junio C HamanoJun 10, 2025
  3. Andrea StacchiottiJun 10, 2025
  4. Junio C HamanoJun 11, 2025
  5. Andrea StacchiottiJun 11, 2025
  6. Junio C HamanoJun 11, 2025
  7. Andrea StacchiottiJun 12, 2025
  8. Junio C HamanoJun 12, 2025
  9. Junio C HamanoJun 12, 2025
  10. Andrea StacchiottiJun 12, 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.