What's the best strategy to implement the git-transport

[mgmart]

As it seems there will be no support for attachments, images or tree-sync in org-mobile.el. Therefore I think the approach should to use git as a transport and fiddle in org-mobile.el later (if it's still necessary).

The best strategy I can think of is that every write from MobileOrg comes be in a separate branch if head is different from the last fetch.

That and a default setting wether MobileOrg or the repository should win if there are conflicts should be sufficient to avoid conflict handling on the mobile device.

I'm not sure if this approach is too naive. I would appreciate any thoughts on this.

[mgmart]

Talking to myself here 😄

My personal org-files reside in many git repositories at the moment. As I publish some of them by using hugo, it is the easiest approach to leave the git repositories separate.

Conclusion would be that git as the main transport is not a feasible approach.