git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hommey <mh@glandium.org>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH v8 0/9] connect: various cleanups
Date: Sat, 28 May 2016 06:59:43 +0900	[thread overview]
Message-ID: <20160527215943.GA21018@glandium.org> (raw)
In-Reply-To: <a6f4bf06-a52b-dcdf-9407-0c03b8b1dfe1@web.de>

On Fri, May 27, 2016 at 04:24:20PM +0200, Torsten Bögershausen wrote:
> On 27.05.16 04:27, Mike Hommey wrote:
> > Changes from v7:
> > - Fixed comments.
> > 
> > Mike Hommey (9):
> >   connect: document why we sometimes call get_port after
> >     get_host_and_port
> >   connect: call get_host_and_port() earlier
> >   connect: re-derive a host:port string from the separate host and port
> >     variables
> >   connect: make parse_connect_url() return separated host and port
> >   connect: group CONNECT_DIAG_URL handling code
> >   connect: make parse_connect_url() return the user part of the url as a
> >     separate value
> >   connect: change the --diag-url output to separate user and host
> >   connect: actively reject git:// urls with a user part
> >   connect: move ssh command line preparation to a separate function
> > 
> >  connect.c             | 235 +++++++++++++++++++++++++++++---------------------
> >  t/t5500-fetch-pack.sh |  42 ++++++---
> >  2 files changed, 170 insertions(+), 107 deletions(-)
> > 
> Is the whole series somewhere on a public repo ?

Is it now :)

> No major remarks so far, if possible, I would like
> to have a look at the resulting connect.c

https://github.com/glandium/git/blob/connect/connect.c

Mike

  reply	other threads:[~2016-05-27 22:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27  2:27 [PATCH v8 0/9] connect: various cleanups Mike Hommey
2016-05-27  2:27 ` [PATCH v8 1/9] connect: document why we sometimes call get_port after get_host_and_port Mike Hommey
2016-05-27  2:27 ` [PATCH v8 2/9] connect: call get_host_and_port() earlier Mike Hommey
2016-05-27  2:27 ` [PATCH v8 3/9] connect: re-derive a host:port string from the separate host and port variables Mike Hommey
2016-05-27  2:27 ` [PATCH v8 4/9] connect: make parse_connect_url() return separated host and port Mike Hommey
2016-05-27  2:27 ` [PATCH v8 5/9] connect: group CONNECT_DIAG_URL handling code Mike Hommey
2016-05-27  2:27 ` [PATCH v8 6/9] connect: make parse_connect_url() return the user part of the url as a separate value Mike Hommey
2016-05-27  2:27 ` [PATCH v8 7/9] connect: change the --diag-url output to separate user and host Mike Hommey
2016-05-27  2:27 ` [PATCH v8 8/9] connect: actively reject git:// urls with a user part Mike Hommey
2016-05-27  2:27 ` [PATCH v8 9/9] connect: move ssh command line preparation to a separate function Mike Hommey
2016-05-27 14:24 ` [PATCH v8 0/9] connect: various cleanups Torsten Bögershausen
2016-05-27 21:59   ` Mike Hommey [this message]
2016-05-28  5:02     ` Torsten Bögershausen
2016-05-28  5:33       ` Mike Hommey
2016-05-28  8:17         ` Torsten Bögershausen
2016-05-28  8:47           ` Mike Hommey

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=20160527215943.GA21018@glandium.org \
    --to=mh@glandium.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).