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

Re: What's cooking in git.git (Jun 2016, #01; Thu, 2)

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 4, 2016, 16:24 UTC
Message-ID
<xmqqinxozzuj.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160604051458.GA3149@glandium.org>
Mike Hommey <mh@glandium.org> writes:
> From my POV, the desired outcome from this patch series is that there is
> no change of behavior, and Torsten's fix makes
> git://[example.com:123]:/path/to/repo urls handled the same before and
> after the patch series.
OK.

I somehow suspect nobody cares too much about what happens to the <scheme>://[<string>] syntax where [<string>] is not an IPv6 literal, but if a rewrite is meant to be a rewrite, it is very good that you two are aiming for bug-to-bug compatible behaviour.

Can we have a final submission to be queued? I'd rather not to squash things in to a topic that I wasn't heavily involved in its review discussion.

Thanks.
Previous: Mike HommeyNext: Torsten Bögershausen
Message 10 of 13 in “What's cooking in git.git (Jun 2016, #01; Thu, 2)”
  1. Junio C HamanoJun 2, 2016
  2. Mike HommeyJun 2, 2016
  3. Torsten BögershausenJun 3, 2016
  4. Junio C HamanoJun 3, 2016
  5. Mike HommeyJun 3, 2016
  6. Junio C HamanoJun 3, 2016
  7. Mike HommeyJun 4, 2016
  8. Torsten BögershausenJun 4, 2016
  9. Mike HommeyJun 4, 2016
  10. Junio C HamanoJun 4, 2016
  11. Torsten BögershausenJun 5, 2016
  12. 1/1 connect: [host:port] is lagacy for sshtboegi@web.de, Jun 5, 2016
  13. Eric SunshineJun 5, 2016

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.