commnet
authorJoey Hess <joeyh@joeyh.name>
Mon, 4 Apr 2022 16:05:21 +0000 (12:05 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 4 Apr 2022 16:05:21 +0000 (12:05 -0400)
doc/bugs/adb_creates_empty_commits_on_import__47__sync/comment_10_87efdd2a9c7091f92a6bc96e87a59e18._comment [new file with mode: 0644]

diff --git a/doc/bugs/adb_creates_empty_commits_on_import__47__sync/comment_10_87efdd2a9c7091f92a6bc96e87a59e18._comment b/doc/bugs/adb_creates_empty_commits_on_import__47__sync/comment_10_87efdd2a9c7091f92a6bc96e87a59e18._comment
new file mode 100644 (file)
index 0000000..d4d6814
--- /dev/null
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 10"""
+ date="2022-04-04T16:03:06Z"
+ content="""
+Well, a change to the inode would change the CID, but what I saw back in
+comment #4 was that a change to the CID when the file content did not
+actually change, did not result in an empty commit. So I still don't
+understand how you are getting empty commits here.
+
+I also don't think all android devices do that, because such a change of
+the inode will mean it needs to re-download the file, and I do not see
+periodic re-downloads of files when syncing with my own android phone.
+"""]]