From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo de Moraes Serpa Subject: Re: Store org-files in a git repository? Date: Mon, 10 Sep 2012 21:18:38 -0500 Message-ID: References: <87fw6sykb8.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf302ef9222bcceb04c963b149 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54694) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TBG3k-0000mo-D2 for emacs-orgmode@gnu.org; Mon, 10 Sep 2012 22:18:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TBG3j-0006h2-5Q for emacs-orgmode@gnu.org; Mon, 10 Sep 2012 22:18:40 -0400 Received: from mail-qc0-f169.google.com ([209.85.216.169]:63652) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TBG3i-0006gq-VM for emacs-orgmode@gnu.org; Mon, 10 Sep 2012 22:18:39 -0400 Received: by qcsd16 with SMTP id d16so4948qcs.0 for ; Mon, 10 Sep 2012 19:18:38 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Moritz Ulrich Cc: Achim Gratz , emacs-orgmode@gnu.org --20cf302ef9222bcceb04c963b149 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable It'd be nice to see how Google Docs does its versioning and try to model something like that for org. I think it's a version per data saved. I currently use a cron, but I see some value in versioning after each save. On Mon, Sep 10, 2012 at 5:23 PM, Moritz Ulrich wrote= : > > Achim Gratz writes: > > > 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 o= r > >> other org functions together with a context dependent commit message. > > > > =BBThe road to hell is paved with good intentions.=AB =97 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. > > > > > > Regards, > > Achim. > > I rarely thought about the problem of transactional operations in > org-mode. From the standpoint you mentioned, my dream doesn't look that > nice anymore. > > A simple cron job for committing doesn't sound that bad anymore ;-) > > Thanks for saving me much work. > > > Cheers, > Moritz Ulrich > > -- > Moritz Ulrich > --20cf302ef9222bcceb04c963b149 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable It'd be nice to see how Google Docs does its versioning and try to mode= l something like that for org. I think it's a version per data saved. I= currently use a cron, but I see some value in versioning after each save.<= br>
On Mon, Sep 10, 2012 at 5:23 PM, Moritz Ulri= ch <moritz@tarn-vedra.de> wrote:

Achim Gratz writes:

> 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 sort= s of
>> org-mode hooks, automatically committing changes done via the agen= da or
>> other org functions together with a context dependent commit messa= ge.
>
> =BBThe road to hell is paved with good intentions.=AB =97 proverb
>
> What you're proposing (if I understand it correctly) would introdu= ce
> transactions to Org and with it the non-trivial problem of determining=
> when a transaction is finished (and started, but that's really ano= ther
> one). =A0Git 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.
>
>
> Regards,
> Achim.

I rarely thought about the problem of transactional operations in
org-mode. From the standpoint you mentioned, my dream doesn't look that=
nice anymore.

A simple cron job for committing doesn't sound that bad anymore ;-)

Thanks for saving me much work.


Cheers,
Moritz Ulrich

--
Moritz Ulrich

--20cf302ef9222bcceb04c963b149--