All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Mike Hommey <mh@glandium.org>
Cc: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2016, #01; Thu, 2)
Date: Sat, 04 Jun 2016 09:24:36 -0700	[thread overview]
Message-ID: <xmqqinxozzuj.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160604051458.GA3149@glandium.org> (Mike Hommey's message of "Sat, 4 Jun 2016 14:14:58 +0900")

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.

  parent reply	other threads:[~2016-06-04 16:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 22:52 What's cooking in git.git (Jun 2016, #01; Thu, 2) Junio C Hamano
2016-06-02 23:13 ` Mike Hommey
2016-06-03  5:07   ` Torsten Bögershausen
2016-06-03 15:59     ` Junio C Hamano
2016-06-03 23:26     ` Mike Hommey
2016-06-03 23:47       ` Junio C Hamano
2016-06-04  5:14         ` Mike Hommey
2016-06-04 14:51           ` Torsten Bögershausen
2016-06-04 21:46             ` Mike Hommey
2016-06-04 16:24           ` Junio C Hamano [this message]
2016-06-05  9:29             ` Torsten Bögershausen
2016-06-05 11:09             ` [PATCH v1 1/1] connect: [host:port] is lagacy for ssh tboegi
2016-06-05 18:56               ` Eric Sunshine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqinxozzuj.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mh@glandium.org \
    --cc=tboegi@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.