public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: "Stéphane Graber" <stgraber@stgraber•org>
Cc: git@vger•kernel.org
Subject: Re: git-send-email and IPv6-only host
Date: Fri, 28 Aug 2015 10:19:09 -0700	[thread overview]
Message-ID: <xmqqbndr2uwi.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20150828041119.GP301234@dakara> ("Stéphane Graber"'s message of "Fri, 28 Aug 2015 00:11:19 -0400")

Stéphane Graber <stgraber@stgraber•org> writes:

> Hello,
>
> I've recently switched my home network to be IPv6-only, using NAT64 and
> DNS64 to reach IPv4 hosts. Pretty much everything I use day to day just
> kept on working fine, but I keep finding some small problems here and
> there, mostly to do with perl software.
>
> One of those is git-send-email which isn't capable of talking to an IPv6
> SMTP server.
>
> I've locally patched my git-send-email to add:
>
>     require Net::INET6Glue::INET_is_INET6;
>
> This seems to be the magic bullet for all IPv6 problems I've had with
> perl software, though I'm not sure whether this is an acceptable fix
> upstream as this does bring an additional dependency to git-send-email.

I wonder what happens if you 'require' that Glue on a host that is
not IPv6-only.

What I am trying to get at is if what that Glue thing does is an
acceptable thing to do in the Net::* Perl modules (e.g. Net::SMTP
and Net::SMTP::SSL that we use), i.e., what INET6Glue does to work
around issues in Net::* is a problem Net::* Perl modules should be
solving for the users of these modules.

After all, it is madness to ask all packages that use Net::*
infrastructure, like git-send-email, to 'require' an extra module.

Thanks.

next prev parent reply	other threads:[~2015-08-28 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  4:11 git-send-email and IPv6-only host Stéphane Graber
2015-08-28 17:19 ` Junio C Hamano [this message]
2015-08-28 17:32   ` Stéphane Graber

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=xmqqbndr2uwi.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=stgraber@stgraber$(echo .)org \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox