From: "'Peter Backes'" <rtc@helen.PLASMA.Xg8.DE>
To: Andreas Krey <a.krey@gmx.de>
Cc: "Randall S. Becker" <rsbecker@nexbridge.com>,
"'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>,
"'Derek Fawcus'" <dfawcus+lists-git@employees.org>,
git@vger.kernel.org, "'Theodore Ts'o'" <tytso@mit.edu>
Subject: Re: Git should preserve modification times at least on request
Date: Mon, 26 Feb 2018 12:04:35 +0100 [thread overview]
Message-ID: <20180226110435.GA23573@helen.PLASMA.Xg8.DE> (raw)
In-Reply-To: <20180226105642.GA6549@inner.h.apk.li>
On Mon, Feb 26, 2018 at 11:56:42AM +0100, Andreas Krey wrote:
> > The bigger issue is usually to copy with those pesky leap seconds. It
> > makes a difference whether one uses solar seconds ("posix" style; those
> > are more commonly seen) or atomic seconds ("right" style) for the UNIX
> > timestamp.
>
> Is there any system, unix or otherwise, that uses 'right'-style seconds,
> i.e. TAI, as its base?
Most certainly there is. This depends on the individual configuration
of the system. On my Fedora system, the commonly used tzdata package
off the shelf contains support for 'right' style versions of all
timezones in /usr/share/zoneinfo/right If the user links one of those
timezones to /etc/localtime or manually specifies them (like
TZ=right/Europe/Berlin ls -l) they will be used.
You don't find a lot of those systems today, but those who used to use
the 'right' timestamps might for legacy reasons explicitly configure
their system to use those timezone variants. I personally did this for
a number of years, but then converted the filesystems timestamps to
'posix' and I am now exclusively using 'posix' ones.
Best wishes
Peter
--
Peter Backes, rtc@helen.PLASMA.Xg8.DE
next prev parent reply other threads:[~2018-02-26 11:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 21:22 Git should preserve modification times at least on request Peter Backes
2018-02-19 21:58 ` Johannes Schindelin
2018-02-19 22:08 ` Peter Backes
2018-02-20 1:22 ` Theodore Ts'o
2018-02-20 10:46 ` Johannes Schindelin
2018-02-20 11:53 ` Peter Backes
2018-02-20 21:05 ` Peter Backes
2018-02-20 22:32 ` Johannes Schindelin
2018-02-20 22:48 ` Peter Backes
2018-02-21 21:30 ` Phillip Wood
2018-02-19 22:37 ` Randall S. Becker
2018-02-19 23:22 ` Hilco Wijbenga
2018-02-20 16:42 ` Hilco Wijbenga
2018-02-20 21:16 ` Jeff King
2018-02-20 22:05 ` Peter Backes
2018-02-21 9:48 ` Jacob Keller
2018-02-20 23:40 ` Junio C Hamano
2018-02-21 21:03 ` Derek Fawcus
2018-02-21 21:33 ` Ævar Arnfjörð Bjarmason
2018-02-21 22:14 ` Peter Backes
2018-02-21 22:44 ` Ævar Arnfjörð Bjarmason
2018-02-21 23:12 ` Peter Backes
2018-02-21 23:58 ` Randall S. Becker
2018-02-22 2:05 ` 'Peter Backes'
2018-02-26 10:56 ` Andreas Krey
2018-02-26 11:04 ` 'Peter Backes' [this message]
2018-02-22 23:24 ` Derek Fawcus
2018-02-23 12:28 ` Konstantin Khomoutov
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=20180226110435.GA23573@helen.PLASMA.Xg8.DE \
--to=rtc@helen.plasma.xg8.de \
--cc=a.krey@gmx.de \
--cc=avarab@gmail.com \
--cc=dfawcus+lists-git@employees.org \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.