You've caught me with two agendas.
> > (.) For backup on USB drive: export or
> > dump rather than checkout/update.
> I'm not sure I understand your goal with this
> last point, since the various concepts your're
> mentioning are used for different purposes.
I've set my girlfriend up with SVN to write her thesis, and created a
script to perform commit and backups. She has a tendency to do
unforeseeably strange things once in a while. I've found that the
export allows her to get back to work quickly while I attempt to
discover what happened in the repository. I had been dumping, but have
found the repository copy easier to work with.
> Were you planning on also keeping your
> working copy(ies) on the USB drive? I
> don't think you mentioned that initially.
For my own work, I may find myself on a computer located, for
discussion, in a cave. If I update the USB's working copy then the
latest files will always be available even when SVN is not. My concern
is that if computer-A with svn 1.3 checks out or updates the working
copy then later, computer-B (with svn 1.1) may not be able to work
with it. There should be no problem if each machine has its own
2006/1/11, Ryan Schmidt <subversion-2006Q1@ryandesign.com>:
> On Jan 11, 2006, at 10:18, Alexander E Genaud wrote:
> > (.) For backup on USB drive: export or dump rather than checkout/
> > update.
> I'm not sure I understand your goal with this last point, since the
> various concepts you're mentioning are used for different purposes.
> You said you were going to have a repository on a USB drive.
> "svnadmin dump" is a command that can be used on a repository to dump
> its entire history to a text file which can later be used to recreate
> the repository should the original repository fail for some reason.
> This is one good method of creating a backup of a repository.
> (Another is the hot-copy method or, for FSFS repositories, simply
> copying the repository directory.)
> "svn export" is an operation that gives you a copy of the HEAD of the
> repository (or of the current state of a working copy, if applied
> instead on a working copy). It does not give you any history, and is
> thus not a strategy for backing up a repository.
> "svn checkout" creates a working copy and "svn update" updates a
> working copy. These are commands you would use with a Subversion
> working copy for the purpose of making changes to the working copy
> and checking these in to the repository. They are not, however, any
> part of a backup strategy.
> Were you planning on also keeping your working copy(ies) on the USB
> drive? I don't think you mentioned that initially. Not that there's
> anything wrong with that, of course; should work fine too. I'm just
> starting to wonder whether your USB drive has space for all this.
CCC7 D19D D107 F079 2F3D BF97 8443 DB5A 6DB8 9CE1
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Jan 11 12:58:07 2006