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

Re: Git merge should report an actual syntax error when a semicolon is used instead of space for specifying multiple branches

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 12, 2019, 07:05 UTC
Message-ID
<xmqqsgunya8j.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<fQ_n3UAoz-yQ8MMCgPLhVDqkMCqpXQ2Dk34IZgksKIQ1B3Sig_T70nPI5mI0z9z2A5ZLdk5ooUYnAJelV-7eMNrnCr4V73Rz87pP1arR8WA=@protonmail.com>
ron <ronazek@protonmail.com> writes:
> ... And it may not be uncommon since it comes from the fact that
> git merge normally follows git fetch where semicolon is supported
> as per normal.

I do not know what "git fetch" uses semicolon for here. Care to elaborate?

Previous: ronNext: Ron
Message 2 of 4 in “Git merge should report an actual syntax error when a semicolon is used instead of space for specifying multiple branches”
  1. ronApr 11, 2019
  2. Junio C HamanoApr 12, 2019
  3. RonApr 12, 2019
  4. Junio C HamanoApr 12, 2019

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.