From: Andreas Schwab <schwab@linux-m68k.org>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH v4 06/11] Provide backward compatibility for strftime family (bug 10871).
Date: Thu, 10 Nov 2016 19:19:00 -0000 [thread overview]
Message-ID: <87k2cbuoq9.fsf@linux-m68k.org> (raw)
In-Reply-To: <856824585.71033.1478803337086@poczta.nazwa.pl> (Rafal Luzynski's message of "Thu, 10 Nov 2016 19:42:17 +0100 (CET)")
On Nov 10 2016, Rafal Luzynski <digitalfreak@lingonborough.com> wrote:
> I was investigating these cases long ago and in Linux only,
> sorry if I'm inaccurate and please tell me if an actual investigation
> is needed again. I don't know if FreeBSD uses the same GNU coreutils
> as Linux does but if it does then it's not a surprise if some bugs
> are common.
FreeBSD generally does not use GNU tools. Here is the source for date,
for example:
https://svnweb.freebsd.org/base/head/bin/date/
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-11-10 19:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 0:49 Rafal Luzynski
2016-11-04 13:40 ` Florian Weimer
2016-11-05 10:53 ` Rafal Luzynski
2016-11-07 14:13 ` Florian Weimer
2016-11-08 11:39 ` Rafal Luzynski
2016-11-09 10:49 ` Florian Weimer
2016-11-10 0:33 ` Rafal Luzynski
2016-11-10 12:41 ` Florian Weimer
2016-11-10 18:42 ` Rafal Luzynski
2016-11-10 19:19 ` Andreas Schwab [this message]
2016-11-15 1:21 ` Rafal Luzynski
2016-11-11 3:52 ` Rical Jasan
2016-11-15 1:38 ` Rafal Luzynski
2016-11-15 11:09 ` Rafal Luzynski
2016-11-16 13:06 ` Rical Jasan
2016-11-17 11:18 ` Rafal Luzynski
2016-11-18 9:22 ` Rical Jasan
2016-11-22 23:56 ` Rafal Luzynski
2016-11-09 11:00 ` Florian Weimer
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=87k2cbuoq9.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=digitalfreak@lingonborough.com \
--cc=fweimer@redhat.com \
--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).