From: Robert Horn <rjhorn@alum.mit.edu>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [SYNC] How do you sync your org-mode files between n devices (n > 2)
Date: Thu, 05 Sep 2013 09:37:53 -0400 [thread overview]
Message-ID: <m361ufz8we.fsf@quad.robs.office> (raw)
In-Reply-To: <m2hadzk2ql.fsf@polytechnique.org>
Alan Schmitt writes:
> I can't promise anything, but I can try to write something. What
> external merging tool should I use?
>
There was some work done in a Summer of Code last year or the year
before. I don't know how much more work remains. It was an effort for
a delta operator for git.
I use a multi-system git environment, and the one area that is beyond
the git capabilities at present is the following kind of problem:
There is a repeating daily task with a log file. On machine A, the task
is finished on Monday, Wednesday, and Friday. On machine B, the task is
finished on Tuesday, Thursday, and Saturday.
Git does not understand the task structure, nor does it understand date
oriented logs. It recognizes that there is a stretch of logfile and
task structure that needs my human intervention and leaves that part for
me to fix. I have to cut the log entries from machine A version and put them
into the log from machine B version in proper date order. The last
complete and next lines will come from machine B because they are more
recent. I understand the date orientation, task structure, etc. Git
does not.
Proper understanding of things like interleaving date related entries is
a difficult task to get right. It would be enough to get it 80% right
with 0% improper fixes, and 20% identified for human merging. But to
reach this level means understanding all the different users of date
tagged lines, entries, headlines, etc. in the org structure.
R Horn
next prev parent reply other threads:[~2013-09-05 13:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 21:34 [SYNC] How do you sync your org-mode files between n devices (n > 2) noreply
2013-09-04 6:04 ` Suvayu Ali
2013-09-04 6:30 ` Xiao-Yong Jin
2013-09-04 7:43 ` Suvayu Ali
2013-09-04 8:00 ` Torsten Wagner
2013-09-05 8:50 ` Alan Schmitt
2013-09-05 9:42 ` Suvayu Ali
2013-09-05 10:00 ` Alan Schmitt
2013-09-05 10:26 ` Karl Voit
2013-09-05 11:42 ` Jonas Hörsch
2013-09-05 13:03 ` [SYNC] How do you sync your org-mode files between ndevices (n > 2)) Alan Schmitt
2013-09-05 11:25 ` [SYNC] How do you sync your org-mode files between n devices (n > 2) Suvayu Ali
2013-09-05 12:31 ` Alan Schmitt
2013-09-05 12:54 ` Suvayu Ali
2013-09-05 13:24 ` Alan Schmitt
2013-09-05 16:14 ` [SYNC] How do you sync your org-mode files between ndevices (n > 2)) Ramon Diaz-Uriarte
2013-09-05 13:37 ` Robert Horn [this message]
2013-09-04 6:21 ` [SYNC] How do you sync your org-mode files between n devices (n > 2) Jambunathan K
2013-09-04 6:47 ` Paul Rudin
2013-09-04 6:50 ` Samuel Loury
2013-09-05 20:00 ` Marc Ihm
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=m361ufz8we.fsf@quad.robs.office \
--to=rjhorn@alum.mit.edu \
--cc=alan.schmitt@polytechnique.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).