From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Zac Medico <zmedico@gentoo.org>
Cc: Ulrich Mueller <ulm@gentoo.org>, gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Re: mtime preservation
Date: Wed, 4 Nov 2009 21:29:19 +0000 [thread overview]
Message-ID: <20091104212919.4fe37274@snowmobile> (raw)
In-Reply-To: <4AF1EE45.20309@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
On Wed, 04 Nov 2009 13:12:37 -0800
Zac Medico <zmedico@gentoo.org> wrote:
> > So far as I can see, if they're fully supported on both filesystems,
> > Portage sometimes preserves nanosecond-resolution timestamps and
> > sometimes doesn't. So, requiring nanosecond-resolution timestamp
> > preservation where possible will need Portage changes.
>
> I think it always preserves them, as long as you have at least
> python-2.5 since that is required for floating-point mtime support.
Mm, I can't see the code for that. So far as I can see, for the
non-fast case you're using stat.st_mtime and os.utime, which assuming
they correspond to the POSIX things of the same name, are
second-resolution. What am I missing?
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-04 21:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 17:03 [gentoo-council] Agenda (draft) for November meeting 2009-11-09 Ulrich Mueller
2009-11-03 18:06 ` Ciaran McCreesh
2009-11-04 15:07 ` [gentoo-council] mtime preservation (was: Agenda (draft) for November meeting 2009-11-09) Ulrich Mueller
2009-11-04 15:28 ` [gentoo-council] " Ciaran McCreesh
2009-11-04 21:12 ` [gentoo-council] Re: mtime preservation Zac Medico
2009-11-04 21:29 ` Ciaran McCreesh [this message]
2009-11-05 5:54 ` Zac Medico
2009-11-05 6:11 ` Ulrich Mueller
2009-11-05 6:18 ` Zac Medico
2009-11-05 9:11 ` Ulrich Mueller
2009-11-05 10:24 ` Ulrich Mueller
2009-11-08 19:14 ` Ciaran McCreesh
2009-11-09 15:18 ` Denis Dupeyron
2009-11-09 15:34 ` Ciaran McCreesh
2009-11-09 15:42 ` Petteri Räty
2009-11-09 16:37 ` Ulrich Mueller
2009-11-09 16:53 ` Ciaran McCreesh
2009-11-10 7:07 ` [gentoo-council] " Ulrich Mueller
2009-11-19 22:12 ` Ciaran McCreesh
2009-11-20 0:14 ` Denis Dupeyron
2009-11-20 0:18 ` Ciaran McCreesh
2009-11-21 0:37 ` Zac Medico
2009-11-23 19:16 ` Ulrich Mueller
2009-11-09 16:36 ` [gentoo-council] " Ulrich Mueller
2009-11-09 17:58 ` Denis Dupeyron
2009-11-09 18:14 ` Ciaran McCreesh
2009-11-09 18:48 ` Denis Dupeyron
2009-11-03 20:17 ` [gentoo-council] Agenda (draft) for November meeting 2009-11-09 Patrick Lauer
2009-11-03 22:56 ` Denis Dupeyron
2009-11-03 23:10 ` Ciaran McCreesh
2009-11-03 23:14 ` Patrick Lauer
2009-11-04 15:19 ` Ulrich Mueller
2009-11-04 15:22 ` Denis Dupeyron
2009-11-05 20:44 ` Ulrich Mueller
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=20091104212919.4fe37274@snowmobile \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-council@lists.gentoo.org \
--cc=ulm@gentoo.org \
--cc=zmedico@gentoo.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