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
RRon <ronazek@protonmail.com>
Date
Apr 12, 2019, 13:37 UTC
Message-ID
<NVqJoDneX4bKnXsESFmcKt_7jDQE8Wk9l_F9rkNcnplXgV8TVjfbaMIhKfZ2v9BwJrJ2QJYcq-E6UdshPdhKttO4bIUGdsbs0zZUPNwQvUY=@protonmail.com>
In-Reply-To
<xmqqsgunya8j.fsf@gitster-ct.c.googlers.com>
> Junio C Hamano <gitster@pobox.com> wrote:
> I do not know what "git fetch" uses semicolon for here. Care to
> elaborate?
Those were all typos, I meant colon, two dots. Sorry.
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 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.