public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] make.globals: fix FETCHCOMMAND_SSH and FETCHCOMMAND_SFTP to respect ssh_config port (bug 499198)
Date: Sat, 7 May 2016 13:26:57 -0700	[thread overview]
Message-ID: <572E4F91.9020906@gentoo.org> (raw)
In-Reply-To: <572DD3BD.7060908@gentoo.org>

On 05/07/2016 04:38 AM, Alexander Berntsen wrote:
> Still barely readable without putting it in git and getting colours.
> Which tells me this should probably not look the way it looks at
> present...

Yeah, we could certainly split the code out into standalone shell
scripts and install them in sub-directory of $PORTAGE_BIN_PATH.

The code makes a good test case for make.* parsing with respect to
quoting and multiple layers of escapes, so maybe we should keep
something similar in the unit tests.

The code was sort of a quick and dirty fix that was never really
intended to be readable, which may have contributed to the 2+ years that
went by before someone got around to writing a patch.

> But it looks like it's doing what it's supposed to be doing. So go
> ahead and push.
> 
> I think the message title is about a billion characters above budget,
> so perhaps just make it "make.globals: Respect ssh_config port (bug
> 499198)" or something; your call though.

Thanks, I've pushed it with your shorter commit message.
-- 
Thanks,
Zac


      reply	other threads:[~2016-05-07 20:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 17:13 [gentoo-portage-dev] [PATCH] make.globals: fix FETCHCOMMAND_SSH and FETCHCOMMAND_SFTP to respect ssh_config port (bug 499198) Zac Medico
2016-05-06 13:11 ` Alexander Berntsen
2016-05-06 16:44 ` Zac Medico
2016-05-07 11:38   ` Alexander Berntsen
2016-05-07 20:26     ` Zac Medico [this message]

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=572E4F91.9020906@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox