[tahoe-dev] [tahoe-lafs] #628: "mtime" and "ctime": I don't think that word means what you think it means.

[tahoe-lafs]

#628: "mtime" and "ctime": I don't think that word means what you think it means.
---------------------------+------------------------------------------------
 Reporter:  zooko          |           Owner:  zooko   
     Type:  defect         |          Status:  assigned
 Priority:  major          |       Milestone:  1.4.0   
Component:  code-dirnodes  |         Version:  1.3.0   
 Keywords:                 |   Launchpad_bug:          
---------------------------+------------------------------------------------

Comment(by zooko):

 Okay here is a new version of my patch which tries harder to leave the old
 {{{mtime}}} and {{{ctime}}} alone so that it won't break the {{{tahoe
 backup}}} command.  It sequesters the new timestamps into a special entry
 of the metadata named {{{__sys}}}, and it spells out their names as
 {{{linkcrtime}}} and {{{linkmotime}}}.  In this patch, the rule of the
 caller setting metadata is simply that the caller can't touch the
 {{{__sys}}} entry, but __can__ continue to overwrite the {{{ctime}}} and
 {{{mtime}}} entries, which I think will make {{{backup}}} pass its unit
 tests again.

 Please review with consideration to whether we could apply a patch like
 this (possibly even a smaller subset of this) for Tahoe-1.4.0.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/628#comment:9>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid