public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "JOSHI, RAHUL" <rahulj@hpe.com>
Cc: "libc-help@sourceware.org" <libc-help@sourceware.org>,
	"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: Having TTL of resolved IP addresses in 'getaddrinfo' or 'getaddrinfo_a'
Date: Mon, 17 May 2021 13:16:34 +0200	[thread overview]
Message-ID: <87bl99k3u5.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CS1PR8401MB0502656334152FB98C735736C02D9@CS1PR8401MB0502.NAMPRD84.PROD.OUTLOOK.COM> (RAHUL JOSHI's message of "Mon, 17 May 2021 11:13:42 +0000")

* RAHUL JOSHI:

> Hi Weimer, we have changes ready in glibc to return TTL for resolved
> IP addresses in 'getaddrinfo'. Can you please let me know what is the
> procedure to raise a request with a patch??

The first step is to ensure that you have permission to post your work
publicly.  This something that you need to clarify with your employer.
Once that is done, you can post your patch.

It is likely that your patch will require FSF copyright assignment, as
described here:

<https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_assignment>

I do not have access to the FSF records and do not know if HPE already
has a copyright assignment on file.

Thanks,
Florian


  reply	other threads:[~2021-05-17 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 11:13 JOSHI, RAHUL
2021-05-17 11:16 ` Florian Weimer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-03  5:59 JOSHI, RAHUL
2021-05-05  8:27 ` JOSHI, RAHUL
2021-05-05  8:33 ` JOSHI, RAHUL
2021-05-05  8:39 ` Florian Weimer
     [not found]   ` <CS1PR8401MB050236FE63C077687BC1C1D7C0599@CS1PR8401MB0502.NAMPRD84.PROD.OUTLOOK.COM>
2021-05-05  9:41     ` JOSHI, RAHUL
2021-05-05 12:27     ` JOSHI, RAHUL
2021-05-06  8:05     ` JOSHI, RAHUL
2021-05-06  9:20       ` Florian Weimer

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=87bl99k3u5.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-help@sourceware.org \
    --cc=rahulj@hpe.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).