From: Robert Goldman <rpgoldman@sift.info>
To: emacs-orgmode@gnu.org
Subject: Re: Subversion for backups?
Date: Thu, 27 Aug 2009 17:27:40 +0000 (UTC) [thread overview]
Message-ID: <loom.20090827T192206-660@post.gmane.org> (raw)
In-Reply-To: 87iqgaa1qi.fsf@fastmail.fm
Matt Lundin <mdl <at> imapmail.org> writes:
>
> Kyle Sexton <ks <at> mocker.org> writes:
>
> > At Wed, 26 Aug 2009 14:49:41 +0200,
> > Rainer Stengele <rainer.stengele <at> online.de> wrote:
> >>
> >> I use subversion to backup and track my org files.
> >> I have a server in my office running the subversion server.
> >>
>
> This is a bit off-topic, but I found the separation of repository and
> working files in SVN a bit cumbersome after a while. You can't view your
> history when you aren't connected to the remote repository, your history
> is in only one place, you have duplicate files in the .svn directories,
> etc.
>
> For this reason I highly recommend a distributed version control system
> such as git, bzr, etc.. You can start locally quite easily ("git init",
> "git add .", "git commit -a") and then decide to create a remote
> repository whenever you'd like.
>
> In fact, there's a nice tutorial on this:
>
> http://orgmode.org/worg/org-tutorials/org-vcs.php
>
>
FWIW, my feelings are the exact opposite of Matt's --- I find the added
complexity of having multiple repositories to manage and the general added
complexity of git quite unwelcome.
If you are trying to keep multiple machines in sync, I find that a centralized
repository scheme is far simpler: all you need to do is manage the relationship
between your working copies and the repository, and that relationship is a very
simple one.
If you have a distributed revision control system and multiple different
repositories, you must manage the relationship between the different
repositories and the relationship between those repositories and your working
copies. Because of the peer-to-peer aspect, this is a complex quadratic mesh of
relationships to manage, instead of the simple linear relationship you have with
a centralized repository.
I would say that if (1) you generally are connected to the internet, with only
minor intervals offline and (2) have access to a hosted svn repository (so you
don't manage it yourself, and so that you can use the simple https protocol
instead of fussing with ssh tunneling), then you are likely to find svn much
simpler. I am fortunate that both of these hold for me.
That said, if you are already a git wizard, this won't apply...
Best,
r
next prev parent reply other threads:[~2009-08-27 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 21:27 Subversion for backups? Kyle Sexton
2009-08-25 22:16 ` Bernt Hansen
2009-08-26 12:49 ` Rainer Stengele
2009-08-26 13:37 ` Kyle Sexton
2009-08-26 13:38 ` Kyle Sexton
2009-08-26 14:30 ` Manish
2009-08-26 18:06 ` Matt Lundin
2009-08-27 17:27 ` Robert Goldman [this message]
2009-11-04 11:49 ` Adam Spiers
2009-11-04 14:01 ` Rick Moynihan
2009-11-10 13:49 ` Eric S Fraga
2009-08-31 15:05 ` Sébastien Vauban
2009-08-31 21:16 ` Rainer Stengele
2009-09-02 15:26 ` Sébastien Vauban
2009-09-05 13:28 ` Greg Newman
2009-09-07 22:31 ` Bastien
2009-09-08 8:42 ` Greg Newman
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=loom.20090827T192206-660@post.gmane.org \
--to=rpgoldman@sift.info \
--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).