GNU logs - #20199, boring messages

Message sent to bug-coreutils@HIDDEN:

Subject: bug#20199: Enhancement request for date's "-d" option: different epochs
Resent-From: "Ulrich Windl" <Ulrich.Windl@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-coreutils@HIDDEN
Resent-Date: Wed, 25 Mar 2015 12:27:02 +0000
Resent-Message-ID: <handler.20199.B.142728640519577 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 20199 <at> debbugs.gnu.org
Message-Id: <5512B781020000A100019960@HIDDEN>
Date: Wed, 25 Mar 2015 13:26:25 +0100
From: "Ulrich Windl" <Ulrich.Windl@HIDDEN>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi!

I'm not subscribed to this list, and I hope this is the right place to =
report an enhancement request as there seems to be no bugzilla for that.
Anyway: When downloading the current leap seconds list for out NTP server =
I realized that the dates there seem to be specified in seconds from =
1900-01-01_00:00:00 on one hand, and on the other I realized that date's =
option "-d" only allows UNIX epochs using the "@" notation.

Therefore I suggest to allow different starting epochs, possible using a =
syntax like "date -d '1900-01-01+2287785599'" to print the date and time =
of 2287785599 seconds past January 1st 1900. ("Like" means I suggest the =
semantics, but are not really proposing a concrete syntax; possibly there =
are smarter guy around than me)

Also being able to decode hexadecimal NTP timestamps would be a nice =
feature: NTp timestamps look like this:
d8bd24ef.a8e2bb68 meaning "Wed, Mar 25 2015 13:13:35.659...", so it's 32 =
bit for the seconds and another 32 bit for the fractional seconds (see =
page 9 of the PostScript or PDF version of RFC 1305: "NTP timestamps are =
represented as a 64-bit
unsigned fixed-point number, in seconds relative to 0h on 1 January 1900. =
The integer part is in the
first 32 bits and the fraction part in the last 32 bits.")

Maybe a "tagged" syntax like "-d NTP:d8bd24ef.a8e2bb6" could be used...

(For consistency other tags like "UNIX:" for the UNIX epoch and "MS-WIN:" =
for Microsoft Windows could be used. Again smart guys probably know more =
important epochs than I do)

Regards,
Ulrich

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.503 (Entity 5.503)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: "Ulrich Windl" <Ulrich.Windl@HIDDEN>
Subject: bug#20199: Acknowledgement (Enhancement request for date's "-d"
 option: different epochs)
Message-ID: <handler.20199.B.142728640519577.ack <at> debbugs.gnu.org>
References: <5512B781020000A100019960@HIDDEN>
X-Gnu-PR-Message: ack 20199
X-Gnu-PR-Package: coreutils
Reply-To: 20199 <at> debbugs.gnu.org
Date: Wed, 25 Mar 2015 12:27:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-coreutils@HIDDEN

If you wish to submit further information on this problem, please
send it to 20199 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
20199: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D20199
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-coreutils@HIDDEN:

Subject: bug#20199: Enhancement request for date's "-d" option: different epochs
Resent-From: =?UTF-8?Q?P=C3=A1draig?= Brady <P@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-coreutils@HIDDEN
Resent-Date: Wed, 25 Mar 2015 13:11:01 +0000
Resent-Message-ID: <handler.20199.B20199.142728901524226 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Ulrich Windl <Ulrich.Windl@HIDDEN>,  20199 <at> debbugs.gnu.org
Message-ID: <5512B3AC.7030509@HIDDEN>
Date: Wed, 25 Mar 2015 13:10:04 +0000
From: =?UTF-8?Q?P=C3=A1draig?= Brady <P@HIDDEN>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
References: <5512B781020000A100019960@HIDDEN>
In-Reply-To: <5512B781020000A100019960@HIDDEN>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

On 25/03/15 12:26, Ulrich Windl wrote:
> Hi!
> 
> I'm not subscribed to this list, and I hope this is the right place to report an enhancement request as there seems to be no bugzilla for that.
> Anyway: When downloading the current leap seconds list for out NTP server I realized that the dates there seem to be specified in seconds from 1900-01-01_00:00:00 on one hand, and on the other I realized that date's option "-d" only allows UNIX epochs using the "@" notation.
> 
> Therefore I suggest to allow different starting epochs, possible using a syntax like "date -d '1900-01-01+2287785599'" to print the date and time of 2287785599 seconds past January 1st 1900. ("Like" means I suggest the semantics, but are not really proposing a concrete syntax; possibly there are smarter guy around than me)
> 
> Also being able to decode hexadecimal NTP timestamps would be a nice feature: NTp timestamps look like this:
> d8bd24ef.a8e2bb68 meaning "Wed, Mar 25 2015 13:13:35.659...", so it's 32 bit for the seconds and another 32 bit for the fractional seconds (see page 9 of the PostScript or PDF version of RFC 1305: "NTP timestamps are represented as a 64-bit
> unsigned fixed-point number, in seconds relative to 0h on 1 January 1900. The integer part is in the
> first 32 bits and the fraction part in the last 32 bits.")
> 
> Maybe a "tagged" syntax like "-d NTP:d8bd24ef.a8e2bb6" could be used...
> 
> (For consistency other tags like "UNIX:" for the UNIX epoch and "MS-WIN:" for Microsoft Windows could be used. Again smart guys probably know more important epochs than I do)

Note offsets can be negative, so you could set the offset like:

  $ sec=1234567890
  $ date -d @$(($sec + $(date -d 1/1/1900 +%s)))
  Tue Feb 14 23:56:51 GMT 1939

cheers,
P�draig.

Message sent to bug-coreutils@HIDDEN:

Subject: bug#20199: Enhancement request for date's "-d" option: different epochs
Resent-From: =?UTF-8?Q?P=C3=A1draig?= Brady <P@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-coreutils@HIDDEN
Resent-Date: Wed, 25 Mar 2015 13:18:01 +0000
Resent-Message-ID: <handler.20199.B20199.142728942724903 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Ulrich Windl <Ulrich.Windl@HIDDEN>,  20199 <at> debbugs.gnu.org
Message-ID: <5512B549.6000500@HIDDEN>
Date: Wed, 25 Mar 2015 13:16:57 +0000
From: =?UTF-8?Q?P=C3=A1draig?= Brady <P@HIDDEN>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
References: <5512B781020000A100019960@HIDDEN>
 <5512B3AC.7030509@HIDDEN>
In-Reply-To: <5512B3AC.7030509@HIDDEN>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

On 25/03/15 13:10, P�draig Brady wrote:
> On 25/03/15 12:26, Ulrich Windl wrote:
>> Hi!
>>
>> I'm not subscribed to this list, and I hope this is the right place to report an enhancement request as there seems to be no bugzilla for that.
>> Anyway: When downloading the current leap seconds list for out NTP server I realized that the dates there seem to be specified in seconds from 1900-01-01_00:00:00 on one hand, and on the other I realized that date's option "-d" only allows UNIX epochs using the "@" notation.
>>
>> Therefore I suggest to allow different starting epochs, possible using a syntax like "date -d '1900-01-01+2287785599'" to print the date and time of 2287785599 seconds past January 1st 1900. ("Like" means I suggest the semantics, but are not really proposing a concrete syntax; possibly there are smarter guy around than me)
>>
>> Also being able to decode hexadecimal NTP timestamps would be a nice feature: NTp timestamps look like this:
>> d8bd24ef.a8e2bb68 meaning "Wed, Mar 25 2015 13:13:35.659...", so it's 32 bit for the seconds and another 32 bit for the fractional seconds (see page 9 of the PostScript or PDF version of RFC 1305: "NTP timestamps are represented as a 64-bit
>> unsigned fixed-point number, in seconds relative to 0h on 1 January 1900. The integer part is in the
>> first 32 bits and the fraction part in the last 32 bits.")
>>
>> Maybe a "tagged" syntax like "-d NTP:d8bd24ef.a8e2bb6" could be used...
>>
>> (For consistency other tags like "UNIX:" for the UNIX epoch and "MS-WIN:" for Microsoft Windows could be used. Again smart guys probably know more important epochs than I do)
> 
> Note offsets can be negative, so you could set the offset like:
> 
>   $ sec=1234567890
>   $ date -d @$(($sec + $(date -d 1/1/1900 +%s)))
>   Tue Feb 14 23:56:51 GMT 1939

Actually we can use date's relative date support for this:

  $ date -d '1900-01-01 +1234567890 seconds'
  Tue Feb 14 23:56:51 GMT 1939

cheers,
P�draig.

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.