On Wed, Oct 30, 2019 at 05:01:56PM +0100, Guillem Jover wrote:
This indeed works in Debian, but I think it's strictly speaking
incorrect according to POSIX, and as such is non-portable.
It's non portable in a way which hasn't been relevant in more than 20
years and as such isn't worth wasting
Hi!
On Wed, 2019-10-30 at 13:09:33 +, Colin Watson wrote:
> First, is this a distinction with a meaningful difference worth spending
> the time on changing it?
Depends, I guess. See below.
> Second, it is not correct to say that the format requires an offset.
> Referring to timezone(3), the
Hi Holger
On Wed, Oct 30, 2019 at 12:42:54PM +, Holger Levsen wrote:
> On Tue, Oct 29, 2019 at 09:00:15PM +0200, Niko Tyni wrote:
> > On Mon, Oct 28, 2019 at 12:28:32PM +0100, Guillem Jover wrote:
> > > Just noticed this change from the changelog. :) UTC is not really a
> > > proper timezone s
Hi Colin,
On Wed, Oct 30, 2019 at 01:09:33PM +, Colin Watson wrote:
[...]
> Since TZ=UTC is technically correct per timezone(3), I'd stick with it
> unless there's a demonstrable practical difference (perhaps
> compatibility on some odd systems?) justifying the effort involved in
> changing it
On Wed, Oct 30, 2019 at 12:42:54PM +, Holger Levsen wrote:
> On Tue, Oct 29, 2019 at 09:00:15PM +0200, Niko Tyni wrote:
> > On Mon, Oct 28, 2019 at 12:28:32PM +0100, Guillem Jover wrote:
> > > Just noticed this change from the changelog. :) UTC is not really a
> > > proper timezone specificatio
Hi,
(changed to: to debian-devel, added the r-b general list as cc: and bcc:ed
Niko and Guillem.)
the following came up in "#791362: perl: build timezone affects
LOCALTIME_{MIN,MAX}":
On Tue, Oct 29, 2019 at 09:00:15PM +0200, Niko Tyni wrote:
> On Mon, Oct 28, 2019 at 12:28:32PM +0100, Guillem J
6 matches
Mail list logo
