Re: [Issue 1256] Ability to preserve last modification time (mtime) of files under version control
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Wed, 11 Nov 2009 10:45:53 +0000
Edmund Wong wrote:
This issue first needs a functional spec, giving the information you
[[[
OUTLINE OF A
FUNCTIONAL (BEHAVIOURAL) SPECIFICATION FOR
MTIME PRESERVATION (ISSUE #1256)
* High-level semantics we are trying to achieve:
- Whenever Subversion puts or modifies a file (or directory?) in the
- Whenever Subversion modifies a file (or directory?) in the WC, and
- What level of control over the behaviour should the users have?
- Backward compatibility issues: ...
* Specification of the behaviour in all the cases:
Data Storage:
Mtime shall be stored in a versioned property named 'svn:mtime' (?).
Behaviour of Each Action:
The behaviour of each svn action that may affect a node in the WC
- add
- import
- commit
- export
- checkout
- update/switch that brings in a change
- update/switch that brings in NO change
- ...
When is the mtime read or written in each case? What if the user
What happens in each case if we request the mtime be set, but no
* Controlling the behaviour:
- An option in the client config file? Does it control whether the
- How does it interact with the "use-commit-times" option?
]]]
If you are interested in designing this feature, please go for it! Lots
(The patch you saw in the issue doesn't appear to have a spec or any
- Julian
------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.