diff options
| author | Joey Hess <joey@kitenet.net> | 2010-06-08 14:43:21 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2010-06-08 14:43:21 -0400 |
| commit | 2be6660a8f3f523905e7c0ba4c36f579ed0d2493 (patch) | |
| tree | 396e13515762b98821d26476aa0a5c4563ee26c8 | |
| parent | cc6ead1d81eacc75914eedb49c8773d6624cca33 (diff) | |
response
| -rw-r--r-- | doc/bugs/pagemtime_in_refresh_mode.mdwn | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/pagemtime_in_refresh_mode.mdwn b/doc/bugs/pagemtime_in_refresh_mode.mdwn index 97146f805..f926ec86c 100644 --- a/doc/bugs/pagemtime_in_refresh_mode.mdwn +++ b/doc/bugs/pagemtime_in_refresh_mode.mdwn @@ -12,3 +12,17 @@ relevant: `if (! $pagemtime{$page}) { [...]`. How would you like to tackle this? --[[tschwinge]] + +> This could be done via a `needsbuild` hook. The hook is passed +> the list of changed files, and it should be safe to call `rcs_getmtime` +> and update the `pagemtime` for each. +> +> That lets the feature be done by a plugin, which seems good, since +> `rcs_getmtime` varies between very slow and not very fast, depending on +> VCS. +> +> AFAICS, the only use case for doing this is if you commit changes and +> then delay pushing them to a DVCS repo. Since then the file mtime will +> be when the change was pushed, not when it was committed. But I've +> generally felt that recording when a change was published to the repo +> of a wiki as its mtime is good enough. --[[Joey]] |