From: Christoph Groth <christoph@grothesque.org>
To: emacs-orgmode@gnu.org
Subject: Re: Cooperating with oneself using the cloud?
Date: Mon, 22 Sep 2014 10:05:07 +0200 [thread overview]
Message-ID: <8738bk9j2k.fsf@grothesque.org> (raw)
In-Reply-To: CAHxk2pAg_=K=Dx-m1bmvDyu4tvA_dMPm6MJMWL28_+bZgXyDkA@mail.gmail.com
If at least one of your computers can be reached from all the others via
ssh, or you can reach all the other computers from one (i.e. there’s a
star topology), you could use unison to synchronize all kinds of files.
This works very reliably and handles modifications in both directions.
I use git for my programming projects, but I find that version control
is not really ideal for simple file synchronization. This is why I
think that DVCs (and specifically git) are not a good solution for sync
(In case that someone is interested in a discussion of these things):
Keeping everything in a single repo is not handy, and solutions (like
“myrepos”) are kludges. Another serious problem with using git for
synchronization is that it’s not able to synchronize git repositories,
as AFAIK it’s not possible/reasonable to keep git repositories under git
themselves. Just imagine the case where you are in the middle of some
work with a git repo (an interactive rebase, for example), and you’d
like to sync and continue on another machine.
With unison this works like a charm, you there’s no automatic resolution
of conflicts. This is not a problem if you run unison at the beginning
and at the end of each session.
next prev parent reply other threads:[~2014-09-22 8:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 10:59 Cooperating with oneself using the cloud? Martin Schöön
2014-09-15 11:06 ` Phil Mason
2014-09-24 16:29 ` Monroe, Will
2014-09-15 11:23 ` Eric Abrahamsen
2014-09-16 7:23 ` Eric S Fraga
2014-09-15 14:51 ` Bruno Bigras
2014-09-16 8:43 ` Ramon Diaz-Uriarte
2014-09-16 19:47 ` Martin Schöön
2014-09-15 19:30 ` Thierry Banel
2014-09-22 8:05 ` Christoph Groth [this message]
2014-09-24 15:07 ` Tim O'Callaghan
[not found] ` <87ppel6n4s.fsf@grothesque.org>
[not found] ` <CAArV04Nb0P4xGZP7SVg+OTV40xcrWScr9T23-H0=5VeciYo+Zw@mail.gmail.com>
2014-09-25 12:10 ` Fwd: " Tim O'Callaghan
2014-09-25 13:50 ` Monroe, Will
2014-09-25 14:17 ` Brett Viren
2014-09-26 14:11 ` Rasmus
2014-09-26 18:58 ` Monroe, Will
2014-10-29 20:13 ` Karl Voit
2014-10-30 8:09 ` Paul Rudin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738bk9j2k.fsf@grothesque.org \
--to=christoph@grothesque.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).