emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rick Moynihan <rick.moynihan@gmail.com>
To: Adam Spiers <orgmode@adamspiers.org>, emacs-orgmode@gnu.org
Subject: Re: Re: Subversion for backups?
Date: Wed, 4 Nov 2009 14:01:23 +0000	[thread overview]
Message-ID: <e85471e30911040601n7c703f87rdc8b07d5d1f47fd1@mail.gmail.com> (raw)
In-Reply-To: <20091104114955.GB18202@atlantic.linksys.moosehall>

2009/11/4 Adam Spiers <orgmode@adamspiers.org>:
>
>> 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.
>
> I disagree - I think using git with a centralized model provides the
> best of both worlds: simplicity but also all the nice benefits of
> decentralization such as offline commit and history access,
> intelligent merging etc.  Lots of people do it this way, e.g.
>
> http://feeding.cloud.geek.nz/2008/12/setting-up-centralied-git-repository.html

+10 :-)

I use git and it's far easier and more robust than using subversion
(which I used prior to git for many years).

I have a private centralised git repo setup which I use to sync
changes in my org files between desktops at work, home and less
frequently my eeepc.  git's superior merging capabilities mean that
it's trivial to merge changes between all machines...  And when they
occaisionally get out of sync (as can always happen... even with a
cron job pushing) it's easily resolved.

I've been bitten by SVN many, MANY times in the past (merging is a
pain, the berkley-db dependency has been broken and poorly managed by
distros in the past, it interacts wierdly with mDNS on some platforms,
the repo sizes are huge, and if left unchecked svn servers will leave
lots of temporary files lying around, and having .svn directories
littered through your directory tree is a pain).  Also the svn repo
needs to be backed up seperately... where as with git you get
distributed backups for free.

By comparison git is hassle free and far more robust.  Though git is
my preference using git, mercurial or bzr would always be preferable
for me over SVN.

YMMV

R.

  reply	other threads:[~2009-11-04 14:01 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
2009-11-04 11:49         ` Adam Spiers
2009-11-04 14:01           ` Rick Moynihan [this message]
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=e85471e30911040601n7c703f87rdc8b07d5d1f47fd1@mail.gmail.com \
    --to=rick.moynihan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@adamspiers.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).