[tahoe-dev] [tahoe-lafs] #628: "mtime" and "ctime": I don't think that word means what you think it means.
tahoe-lafs
trac at allmydata.org
Wed Feb 25 08:02:22 PST 2009
#628: "mtime" and "ctime": I don't think that word means what you think it means.
---------------------------+------------------------------------------------
Reporter: zooko | Owner:
Type: defect | Status: new
Priority: major | Milestone: 1.3.1
Component: code-dirnodes | Version: 1.3.0
Keywords: | Launchpad_bug:
---------------------------+------------------------------------------------
Changes (by zooko):
* version: 1.2.0 => 1.3.0
* milestone: undecided => 1.3.1
Comment:
This is the sort of thing that I'm motivated to fix and deploy sooner
rather than later. (I think my motivation is because people are starting
to build on top of tahoe, and someone might start to rely on the naming
and semantics of this metadata, so the sooner we change it the less
backwards-compatibility problem we have.) So I'm putting this into the
"1.3.1" milestone.
Of course, most of what is currently being put into the "1.3.1" milestone
isn't actually going to get done in time for a 1.3.1 release, but at least
we can see that it is the kind of change that *would* be appropriate for
1.3.1 if someone were to do the work to fix it. :-)
Also, nobody should do this until Brian comments on this ticket about my
proposal that we stop reading the ctime from the local filesystem, or that
if we do read the ctime from the local filesystem, that we then switch on
platform type, and if Windows then put the value we read into a metadata
element named "create time", else put the value we read into a metadata
element named "change time" ("change time" is, I think, the official
expansion of the unix abbreviation "ctime"). Also that we store the
"mtime" in an element named "modify time".
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/628#comment:4>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
More information about the tahoe-dev
mailing list