From: Paul Eggert <eggert@cs.ucla.edu>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: libc-alpha@sourceware.org, joseph@codesourcery.com
Subject: Re: [PATCH v4 1/2] Port shared code information from the wiki
Date: Mon, 23 Aug 2021 18:16:01 -0700 [thread overview]
Message-ID: <627a1c74-bd9e-6ce4-caff-7c126e01931b@cs.ucla.edu> (raw)
In-Reply-To: <20210823025410.590471-2-siddhesh@sourceware.org>
On 8/22/21 7:54 PM, Siddhesh Poyarekar via Libc-alpha wrote:
> +# The headers on most of these files indicate that glibc is the canonical
> +# source for these files, although in many cases there seem to be useful
> +# changes in the gnulib versions that could be merged back in. Not all gnulib
> +# files contain such a header and it is not always consistent in its format, so
> +# it would be useful to make sure that all gnulib files that are using glibc as
> +# upstream have a greppable header.
For files shared (or close to being shared and intended to be shared
eventually) between glibc and gnulib, please see gnulib/config/srclist.txt.
https://git.savannah.gnu.org/cgit/gnulib.git/plain/config/srclist.txt
Some of these shared files (intprops.h, flexmembers.h) are edited in
PATCH v4 2/2. Although I don't object to those two edits I suggest going
through srclist.txt and making sure we're not going overboard here.
next prev parent reply other threads:[~2021-08-24 1:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 2:54 [PATCH v4 0/2] Source attribution cleanups Siddhesh Poyarekar via Libc-alpha
2021-08-23 2:54 ` [PATCH v4 1/2] Port shared code information from the wiki Siddhesh Poyarekar via Libc-alpha
2021-08-24 1:16 ` Paul Eggert [this message]
2021-08-30 20:46 ` Carlos O'Donell via Libc-alpha
2021-08-30 21:20 ` Carlos O'Donell via Libc-alpha
2021-08-23 2:54 ` [PATCH v4 2/2] Remove "Contributed by" lines Siddhesh Poyarekar via Libc-alpha
2021-08-30 21:20 ` Carlos O'Donell via Libc-alpha
2021-08-30 21:22 ` [PATCH v4 0/2] Source attribution cleanups Carlos O'Donell via Libc-alpha
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://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=627a1c74-bd9e-6ce4-caff-7c126e01931b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@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).