public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Soumendra Ganguly <soumendra@tamu.edu>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: libc-help <libc-help@sourceware.org>
Subject: Re: tcgetwinsize() and tcsetwinsize()
Date: Sun, 13 Dec 2020 03:53:15 -0600	[thread overview]
Message-ID: <CAB4CD3ZysPjbUvmrdCaeBGY24wSXeAZev_DxL+MQoGeRDqx=Gw@mail.gmail.com> (raw)
In-Reply-To: <87ft4aqd67.fsf@mid.deneb.enyo.de>

Sir,
    Thank you for the prompt reply. I will sign the copyright
agreement; the university is not involved in this in any way.

On 12/13/20, Florian Weimer <fw@deneb.enyo.de> wrote:
> * Soumendra Ganguly via Libc-help:
>
>> https://urldefense.com/v3/__https://www.austingroupbugs.net/view.php?id=1151*c3856__;Iw!!KwNVnqRv!RnSGEQ2iUrHEx6eRkz_4mpgwbp-w4dc8VQXkzWh3BY9nLh_d9wbDxg-Y7Q5uJXb8$
>> , tcgetwinsize()
>> and tcsetwinsize() for getting/setting tty winsize are going to appear
>> in POSIX.1 issue 8. NetBSD already has them:
>>
>> 1.
>> https://urldefense.com/v3/__http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/termios/tcgetwinsize.c?only_with_tag=MAIN__;!!KwNVnqRv!RnSGEQ2iUrHEx6eRkz_4mpgwbp-w4dc8VQXkzWh3BY9nLh_d9wbDxg-Y7Wzl4Tds$
>>
>> 2.
>> https://urldefense.com/v3/__http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/termios/tcsetwinsize.c?only_with_tag=MAIN__;!!KwNVnqRv!RnSGEQ2iUrHEx6eRkz_4mpgwbp-w4dc8VQXkzWh3BY9nLh_d9wbDxg-Y7dEzxq5f$
>>
>>
>> Also, musl-libc has them. Would implementations of these functions
>> using ioctl()+TIOCGWINSZ?TIOCSWINSZ be welcome?
>
> An addition would seem reasonable.  The proposed POSIX change appears
> to be compatible with what we have today.
>
> Please note that glibc patches of this size will need copyright
> assignment:
>
>
> <https://urldefense.com/v3/__https://sourceware.org/glibc/wiki/Contribution*20checklist*FSF_copyright_assignment__;JSM!!KwNVnqRv!RnSGEQ2iUrHEx6eRkz_4mpgwbp-w4dc8VQXkzWh3BY9nLh_d9wbDxg-Y7Xft-lqA$
>>
>
> If your contribution is potentially covered by your university, the
> FSF will likely ask for a copyright disclaimer or assignment from them
> as well.
>
> Unfortunately, I have no view into the FSF copyright assignment
> process, but I will be able to help you to get your patch ready for
> integration into glibc.
>

      reply	other threads:[~2020-12-13  9:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-13  6:42 Soumendra Ganguly
2020-12-13  9:16 ` Florian Weimer
2020-12-13  9:53   ` Soumendra Ganguly [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='CAB4CD3ZysPjbUvmrdCaeBGY24wSXeAZev_DxL+MQoGeRDqx=Gw@mail.gmail.com' \
    --to=soumendra@tamu.edu \
    --cc=fw@deneb.enyo.de \
    --cc=libc-help@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).