On 2020-02-24 at 03:59:25, On Luk wrote:
> Hi Sir/Madam,
> 
> I tried to report this issue to dropbox technical team, but they replied that the issue was not caused by Dropbox, so I try to report to your team as a bug report below:
> 
> Everytime I used git to push commit to my remote repo located in my dropbox, some files stuck in syncing status and can’t be able to sync to dropbox. To get those files be synced, I need to do one of the follow steps everytime by manually:
> 
> 1.	Drag and drop back the file to dropbox using the finder.
> OR
> 2.	Click Pause and resume syncing in dropbox desktop manager.
> OR
> 3.	Restart Dropbox.
> 
> To make it clear, I prepared a screen recording to show the issue that I am facing.
> 
> www.dropbox.com/s/ivn7qytk0u67v6n/Screen%20Recording%202020-01-03%20at%2012.21.21%20PM.mov?dl=0
> 
> This issue only appear after I switch to use my new computer running as macOS 10.15, everything works fine in my old computer running as macOS 10.13.6.

In general, using Dropbox or other file syncing programs that sync file
by file is a bad idea.  The state of a Git repository cannot be
represented on a file-by-file basis, and these file syncing programs
cannot replicate the POSIX semantics required for data integrity.  This
is just a limitation of those tools and how they work.

If you must sync your Git repository using Dropbox, it would be better
to have a post-receive hook in your destination repository that packages
the repository using git bundle and stores that in the Dropbox folder to
sync from.

Whether Dropbox does or does not sync files is definitely a Dropbox
issue, and not a Git issue.  Git knows nothing about Dropbox and does
not interact with it in any meaningful way.

> The information in this electronic mail ("e-mail") message is for
> the use of the named recipient(s) only and may be confidential. The
> information may be protected by privilege, work product immunity or other
> applicable law. If you are not the intended recipient(s), the retention,
> dissemination, distribution or copying of this e-mail message is strictly
> prohibited. If you receive this e-mail message in error, please notify me
> immediately by replying to the message and thereafter, delete all copies on
> your system and destroy any hard copies. 

In general, you should not send notices like this to mailing lists,
since they make no sense there, and use a different email address to
send to mailing lists if your job requires these kinds of notices.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204