All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Mike Hommey <mh@glandium.org>, Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, tboegi@web.de
Subject: Re: What's cooking in git.git (Jun 2016, #01; Thu, 2)
Date: Fri, 3 Jun 2016 07:07:18 +0200	[thread overview]
Message-ID: <57511086.40206@web.de> (raw)
In-Reply-To: <20160602231315.GA22864@glandium.org>

On 06/03/2016 01:13 AM, Mike Hommey wrote:
> On Thu, Jun 02, 2016 at 03:52:41PM -0700, Junio C Hamano wrote:
>> * mh/connect (2016-06-01) 9 commits
>>   - connect: move ssh command line preparation to a separate function
>>   - connect: actively reject git:// urls with a user part
>>   - connect: change the --diag-url output to separate user and host
>>   - connect: make parse_connect_url() return the user part of the url as a separate value
>>   - connect: group CONNECT_DIAG_URL handling code
>>   - connect: make parse_connect_url() return separated host and port
>>   - connect: re-derive a host:port string from the separate host and port variables
>>   - connect: call get_host_and_port() earlier
>>   - connect: document why we sometimes call get_port after get_host_and_port
>>
>>   Needs review.
> I /think/ Torsten reviewed it all, and his last comments are in
> $gmane/295800. It's still not clear to me why he wants to remove the
> comment about [].
There where 2 comments in the review.
The most important thing is that now
git://[example.com:123]/path/to/repo is valid, but it shouldn't.
This patch fixes it:

@@ -673,7 +669,7 @@ static enum protocol parse_connect_url(const char *url_orig, char **ret_user,
          * "host:port" and NULL.
          * To support this undocumented legacy we still need to split the port.
          */
-       if (!port)
+       if (!port && protocol == PROTO_SSH)


The other thing is that I asked for a test case for
git://[example.com:123]/path/to/repo
which shouldn't be hard to do.

If nobody else things that this comment in the code is stale:
-       /*
-        * Don't do destructive transforms as protocol code does
-        * '[]' unwrapping in get_host_and_port()
-        */

then just leave it as it is.
Thanks

  reply	other threads:[~2016-06-03  5:08 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 [this message]
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
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=57511086.40206@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mh@glandium.org \
    /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.