emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Store org-files in a git repository?
Date: Sat, 08 Sep 2012 10:45:31 +0200	[thread overview]
Message-ID: <87fw6sykb8.fsf@Rainer.invalid> (raw)
In-Reply-To: m21uidxviy.fsf@tarn-vedra.de

Moritz Ulrich writes:
> I plan to put my org directory (where I keep among other my agenda
> files) under version control and would like to have some sort of
> specialized function for that.
> My dream setup would be a range of functions hooking into all sorts of
> org-mode hooks, automatically committing changes done via the agenda or
> other org functions together with a context dependent commit message.

»The road to hell is paved with good intentions.« — proverb

What you're proposing (if I understand it correctly) would introduce
transactions to Org and with it the non-trivial problem of determining
when a transaction is finished (and started, but that's really another
one).  Git would merely be the mechanism to record the transactions and
probably not a good one at that even with the merge driver.

THat aside, even if it worked I'm sure it would annoy me so much I'd
switch it off entirely.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:

  parent reply	other threads:[~2012-09-08  8:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 23:28 Store org-files in a git repository? Moritz Ulrich
2012-09-07 23:57 ` Marcelo de Moraes Serpa
2012-09-08  0:26   ` Charles Philip Chan
2012-09-08  8:45 ` Achim Gratz [this message]
2012-09-10 22:23   ` Moritz Ulrich
2012-09-11  2:18     ` Marcelo de Moraes Serpa
2012-09-11 18:11       ` Achim Gratz
2012-09-14 11:15     ` Bernt Hansen
2012-09-12 14:18 ` Bastien
2012-09-12 16:52   ` Samuel Wales
2012-09-13 18:05     ` Marcelo de Moraes Serpa

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:

  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=87fw6sykb8.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).