comment
This commit is contained in:
parent
9e18cd28ad
commit
0584e096d1
2 changed files with 18 additions and 0 deletions
|
@ -202,6 +202,7 @@ retrieve' serial src dest =
|
||||||
showOutput -- make way for adb pull output
|
showOutput -- make way for adb pull output
|
||||||
liftIO $ boolSystem "adb" $ mkAdbCommand serial
|
liftIO $ boolSystem "adb" $ mkAdbCommand serial
|
||||||
[ Param "pull"
|
[ Param "pull"
|
||||||
|
, Param "-a"
|
||||||
, File $ fromAndroidPath src
|
, File $ fromAndroidPath src
|
||||||
, File dest
|
, File dest
|
||||||
]
|
]
|
||||||
|
|
|
@ -0,0 +1,17 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 1"""
|
||||||
|
date="2022-01-03T17:48:38Z"
|
||||||
|
content="""
|
||||||
|
Git does not preserve timestamps. So this is kind of out of scope.
|
||||||
|
|
||||||
|
While git-annex will sometimes preserve timestamps when it's easy to do so,
|
||||||
|
there are no guarantees. Most special remotes do not preserve any
|
||||||
|
timestamps in either direction.
|
||||||
|
|
||||||
|
It might be that `adb pull -a` would fix this. But that also preserves
|
||||||
|
the permissions, and pulling in random permissions for annex object files
|
||||||
|
could lead to arbitrary breakage (imagine a suid executable for example).
|
||||||
|
So it would need to clear the permissions. The complexity does not seem
|
||||||
|
worth trying to support a thing that is generally out of scope.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue