bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: bug-gnulib@gnu.org
Subject: Re: Seeking input from developers: glibc copyright assignment policy.
Date: Wed, 16 Jun 2021 14:47:13 +0300	[thread overview]
Message-ID: <20210616114713.GA9394@altlinux.org> (raw)
In-Reply-To: <9b5fff12-c16f-799f-6178-000b2e667d24@cs.ucla.edu>

On Mon, Jun 14, 2021 at 01:39:26PM -0700, Paul Eggert wrote:
> A proposal to change the glibc copyright assignment policy is being 
> circulated on libc-alpha. The email thread starts at 
> <https://sourceware.org/pipermail/libc-alpha/2021-June/127581.html>, and 
> the text of the email seeking input is at the end of this message.
> 
> I'm sending this to bug-gnulib because we copy some files directly from 
> glibc and eventually I expect these files to be affected. The simplest 
> approach I see for Gnulib is to adopt glibc's policy, at least for files 
> or code copied from glibc.

Here is the list of affected gnulib modules:

$ git grep -A1 ^Maintainer: modules/ | sed -n '/glibc/ s/-[^-]*$//p'
modules/alphasort
modules/argp
modules/atoll
modules/crypto/md5
modules/crypto/md5-buffer
modules/dynarray
modules/eloop-threshold
modules/error
modules/euidaccess
modules/filename
modules/fnmatch
modules/fnmatch-h
modules/getcwd
modules/getopt-gnu
modules/getopt-posix
modules/getpass
modules/getpass-gnu
modules/getsubopt
modules/glob
modules/glob-h
modules/idx
modules/inet_ntop
modules/inet_pton
modules/memchr
modules/memcmp
modules/memrchr
modules/mktime
modules/nstrftime
modules/obstack
modules/posix_spawn
modules/posix_spawn-internal
modules/posix_spawn_file_actions_addclose
modules/posix_spawn_file_actions_adddup2
modules/posix_spawn_file_actions_addopen
modules/posix_spawn_file_actions_destroy
modules/posix_spawn_file_actions_init
modules/posix_spawnattr_destroy
modules/posix_spawnattr_getflags
modules/posix_spawnattr_getpgroup
modules/posix_spawnattr_getschedparam
modules/posix_spawnattr_getschedpolicy
modules/posix_spawnattr_getsigdefault
modules/posix_spawnattr_getsigmask
modules/posix_spawnattr_init
modules/posix_spawnattr_setflags
modules/posix_spawnattr_setpgroup
modules/posix_spawnattr_setschedparam
modules/posix_spawnattr_setschedpolicy
modules/posix_spawnattr_setsigdefault
modules/posix_spawnattr_setsigmask
modules/posix_spawnp
modules/pt_chown
modules/putenv
modules/random
modules/random_r
modules/rawmemchr
modules/scandir
modules/scratch_buffer
modules/spawn
modules/stpcpy
modules/stpncpy
modules/strchrnul
modules/strcspn
modules/strdup
modules/strdup-posix
modules/strndup
modules/strpbrk
modules/strptime
modules/strsignal
modules/strtok_r
modules/strtol
modules/strtoll
modules/strtoul
modules/strtoull
modules/strverscmp
modules/timegm
modules/tsearch


-- 
ldv


      parent reply	other threads:[~2021-06-16 11:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 20:39 Seeking input from developers: glibc copyright assignment policy Paul Eggert
2021-06-14 22:46 ` Bruno Haible
2021-06-15 12:03 ` Eric Blake
2021-06-15 16:32   ` Paul Smith
2021-06-15 17:14     ` Bruno Haible
2021-06-16 11:31     ` Eli Zaretskii
2021-06-15 21:08   ` Pádraig Brady
2021-06-16 13:10     ` Paul Smith
2021-06-16 11:47 ` Dmitry V. Levin [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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210616114713.GA9394@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=bug-gnulib@gnu.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).