From: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: Store org-files in a git repository?
Date: Tue, 11 Sep 2012 20:11:44 +0200 [thread overview]
Message-ID: <87vcfka0pr.fsf@Rainer.invalid> (raw)
Marcelo de Moraes Serpa writes:
> 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.
That doesn't solve the problem. A commit is named commit for a reason:
one assumption is that the change it effects is complete and (in the
case of software) it compiles and runs. There is good reason not to
infer anything like that from the simple fact that I've saved the file.
In fact, stashes in Git are just recognition that sometimes you simply
don't want to make that "commitment", but need to store something away
that is not quite complete.
If you want to see "saving is versioning" in action, try (open)VMS. Or
customize Emacs so that it does versioned backup files. It is
occasionally useful to do that, but just like with RCS, versioning of
single files only gets you so far before things break.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
next prev parent reply other threads:[~2012-09-11 18:12 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
2012-09-10 22:23 ` Moritz Ulrich
2012-09-11 2:18 ` Marcelo de Moraes Serpa
2012-09-11 18:11 ` Achim Gratz [this message]
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
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 \
* 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).