You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that currently, the "last changed" dates etc. are not stored and
therefore not propagated to clients... This kind of messed up my pictures
library for all files that did not have the "date taken" metadata set within
the file - which was true for a lot of old pictures and basically all videos
:-/.
I think that this file information should be transferred to all clients. First
one to commit a file should also commit file metadata, others to check out that
file should have the metadata set to the respective values.
Original issue reported on code.google.com by jannis.u...@stoppe.de on 12 Dec 2012 at 11:22
The text was updated successfully, but these errors were encountered:
Yes, this is a highly desirable feature.
However, note that since the very first release, Boar actually already stores
the "modified" and "changed" timestamps from the file system when you check in
or import files. It just doesn't restore this information when checking out. So
if you've used Boar to import your video files, the timestamps are not lost,
merely slightly inaccessible.
Original comment by ekb...@gmail.com on 12 Dec 2012 at 11:50
Changed title: File mtime and ctime should be restored on check-out
That's good to know... This way, I don't have to come up with a script that
guesses the dates from the other files in the directory - and it sounds like it
shouldn't be too hard to implement. Now I just have to somehow make sure that
consecutive checkins don't overwrite the dates, correct?
Original comment by jannis.u...@stoppe.de on 12 Dec 2012 at 12:37
I was googling quite a bit for a backup system for photos, and boar seems to be
the best tool for that, good job! However, the changed timestapms makes it a
no-go for me
Original comment by markus.l...@gmail.com on 29 Apr 2013 at 7:53
Original issue reported on code.google.com by
jannis.u...@stoppe.de
on 12 Dec 2012 at 11:22The text was updated successfully, but these errors were encountered: