From: Joseph Myers <joseph@codesourcery.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Albert ARIBAUD <albert.aribaud@3adev.fr>,
<libc-alpha@sourceware.org>, <bug-gnulib@gnu.org>
Subject: Re: [PATCH 1/1] Y2038: add function __difftime64
Date: Tue, 17 Jul 2018 20:40:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1807172033070.19759@digraph.polyomino.org.uk> (raw)
In-Reply-To: <90246a4c-86cc-c191-8564-e6eea556fa13@cs.ucla.edu>
On Thu, 5 Jul 2018, Paul Eggert wrote:
> Although Gnulib hasn't needed a difftime module yet, it might need one once
> this 32- vs 64-bit time_t stuff lands into glibc, so let's keep difftime.c
> usable for Gnulib.
I don't think we should make such requests of contributers for code that
is not shared with another project. For code that is actually shared with
gnulib (possibly with some divergence on both sides), yes, but not for
arbitrary other functions simply because they might hypothetically be
useful in other context in future.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-07-17 20:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 12:14 [PATCH 0/1] Y2038 support batch 3 - difftime Albert ARIBAUD (3ADEV)
2018-06-20 12:14 ` [PATCH 1/1] Y2038: add function __difftime64 Albert ARIBAUD (3ADEV)
2018-06-20 19:29 ` Paul Eggert
2018-06-20 20:55 ` Albert ARIBAUD
2018-06-21 21:17 ` Paul Eggert
2018-06-25 22:32 ` Albert ARIBAUD
2018-06-25 23:56 ` Paul Eggert
2018-06-27 11:03 ` Albert ARIBAUD
2018-07-05 18:36 ` Albert ARIBAUD
2018-07-05 19:13 ` Zack Weinberg
2018-07-05 19:40 ` Paul Eggert
2018-07-05 20:38 ` Albert ARIBAUD
2018-07-05 21:17 ` Bruno Haible
2018-07-06 5:06 ` Albert ARIBAUD
2018-07-06 22:54 ` Paul Eggert
2018-07-06 22:40 ` Paul Eggert
2018-07-06 22:37 ` Paul Eggert
2018-07-17 20:40 ` Joseph Myers [this message]
2018-07-05 20:50 ` time_t in gnulib Bruno Haible
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=alpine.DEB.2.20.1807172033070.19759@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=albert.aribaud@3adev.fr \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@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).