From: Florian Weimer <fw@deneb.enyo.de>
To: Soumendra Ganguly via Libc-help <libc-help@sourceware.org>
Cc: Soumendra Ganguly <soumendra@tamu.edu>
Subject: Re: tcgetwinsize() and tcsetwinsize()
Date: Sun, 13 Dec 2020 10:16:00 +0100 [thread overview]
Message-ID: <87ft4aqd67.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CAB4CD3ZWtPDdHn+U-ak=VQ57BqadvFCpt-cJ5bX75U0npco-dA@mail.gmail.com> (Soumendra Ganguly via Libc-help's message of "Sun, 13 Dec 2020 00:42:42 -0600")
* Soumendra Ganguly via Libc-help:
> https://www.austingroupbugs.net/view.php?id=1151#c3856, tcgetwinsize()
> and tcsetwinsize() for getting/setting tty winsize are going to appear
> in POSIX.1 issue 8. NetBSD already has them:
>
> 1. http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/termios/tcgetwinsize.c?only_with_tag=MAIN
> 2. http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/termios/tcsetwinsize.c?only_with_tag=MAIN
>
> 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://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_assignment>
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.
next prev parent reply other threads:[~2020-12-13 9:16 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 [this message]
2020-12-13 9:53 ` Soumendra Ganguly
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=87ft4aqd67.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-help@sourceware.org \
--cc=soumendra@tamu.edu \
/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).