investigated file formats; appending timestamp should preserve back-compat
This commit is contained in:
parent
6a6ea06cee
commit
e139a99aa0
1 changed files with 16 additions and 2 deletions
|
@ -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.
|
||||
|
|
Loading…
Reference in a new issue