diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-10-05 16:35:01 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-10-05 16:35:01 -0400 |
| commit | e139a99aa0528af28de8544564e99562d2333d64 (patch) | |
| tree | e3f6e76e1b27ddb14fa5434f742f5af1ca35d844 | |
| parent | 6a6ea06cee8ce69f391f7ce78b98b8f26a599e66 (diff) | |
investigated file formats; appending timestamp should preserve back-compat
| -rw-r--r-- | doc/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.mdwn | 18 |
1 files changed, 16 insertions, 2 deletions
diff --git a/doc/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.mdwn b/doc/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.mdwn index af140403f..2724611fb 100644 --- a/doc/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.mdwn +++ b/doc/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.mdwn @@ -13,5 +13,19 @@ as is done with the other log files, then git-annex can consistently pick the newest value -- which is as close to the "right" value as can be determined in this situation. -(For backwards compatability, git-annex should -treat lines with no timestamp as being timestamped with 0.) +---- + +File format backwards-compatability is the issue. Ideally, old git-annex +would keep working, ignoring the timestamp. + +- uuid.log: "uuid description timestamp" would work; old git-annex + would just treat the timestamp as part of the description which would be + ok +- trust.log: "uuid trustlevel timestamp" would work; old git-annex + ignores trailing words +- remote.log: "uuid key=value ... timestamp" is on the edge but does work + (old git-annex will include the timestamp in the key/value map it builds, + but that should not break anything really) + +Appending "timestamp=xxxxx" would be good for clarity, and make +it easier to parse the timestamp out from lines that have it. |