1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
When adding files to git annex, softlinks are created with current atime (and ctime, etc). Instead, the atime of the added file should be used and added to the meta-data, restoring it everywhere an annex is cloned to. -- RichiH
Optionally, editing the meta-data should change the times in all annexes.
> Thing is, git does not preserve file timestamps much at all.
> It's not uncommon for a `git checkout` to or `git update` to
> mess up timestamps. This is why things like metastore exist (and
> metastore should work ok with git annexed files too). Trying to
> make annexed file symlinks have better timestamp handling than regular
> files in git seems pointless. --[[Joey]]
> > Improving an area where git is (not yet?) good at still makes sense, imo. Photos and the like need absolute timestamps more than source code which is fine with relative timestamps (local builds & updates). Maintaining global timestamps for source code could even cause a lot of unwanted effects. As it is, this issue is the only, but a major, blocker for me before I can start adapting git-annex. As I have three different use cases for it, this is a shame. Unfortunately, I don't speak any Haskell so scratching my own itch isn't do-able (without major effort and not soon, at least). Is there a realistic chance that you will tackle this nonetheless or is this WONTFIX? -- RichiH
>>> Not quite WONTFIX. git-annex should at least, when adding new files,
>>> preserve their timestamp in the symlink it creates.
>>>
>>> Since it doesn't have anything to do with maintaining the symlinks
>>> during an update, or a clone, etc, maintaining the permissions of them
>>> is also out of scope, and it's best to just use metastore if you need
>>> it. Otherwise, git-annex would have to reimplement metastore, and is
>>> unlikely to do it better.
|
