On 06/09/05, Ryan Schmidt <subversion-2005@ryandesign.com> wrote:
> Sorry if I wasn't clear earlier, but yes, what you've described above
> is exactly how you do things in Subversion.
Great. Interesting that I didn't get that from the 'book',
rather, from a Google search.
>
> You said you imported your project successfully. That means you
> already used "svnadmin create" to create a repository, and you had a
> directory which contained your project, and you used "svn import" to
> put it into the repository.
Yep. But that was on the server (FC4)
>
> To continue working, you should now have deleted the local directory
> that you imported, and created a new working copy of what's in the
> repository by using "svn checkout".
No... but I will do (now :-)
Now you work in your new working
> copy as you normally would to work on your project, editing existing
> files, adding new files (and using "svn add" on them to inform
> Subversion that they should become part of the repository)
I find that sort of non-intuitive.
AFAIK, its when I do the commit that they become
part of the 'master' repository?
Not when I 'add' them?
and moving
> or renaming files (with "svn mv"), and using "svn commit" when you're
> done with a batch of work to save it to the repository.
Doesn't ' svn mv'
move them *within* the repo?
>
> I'm surprised you had trouble after reading the book.... It was all
> fairly clear to me after I read it,
based on my prejudice, I might suggest
you knew too much when you read it?
>and I had no background in
> version control.
Ditto. Failed miserably to use CVS.
If you see any specific parts of the book that could
> have been clearer to enhance your understanding, please tell; I think
> the author is always looking for constructive criticism.
As an author, I'm aware of (and reluctant to give feedback) on other
peoples work.
http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-9-sect-1.2-re-add
says
'Add files, directories, or symbolic links to your working copy and
schedule them for addition to the repository.'
Not quite true?
My crude view is,
move files into 'working directory' (no glossary to define this
overloaded definition?)
do an add
do a commit
that 'adds' them to the repo?
More to the point.
I installed svn on apache (the ... webdav thingy was easy, but I
missed it first time)
no problem.
The client side on Windows was easy... except I'd used the cygwin before, so
adding the single dll (why can't it be included inthe download?) was easy.
Why is the DFDS vs Berkely db mentioned in a new install?
It may well be significant history, but it's still history IMHO, if
its not an issue
with a new install?
Enough.
I wanted to sync n machines with one set of files.
subversion seems as if it will work out well for my needs.
either way, thanks for the tips Ryan.
btw
How do I stop the server being readable by anyone using svn co <url>?
Or was that just because I'd saved a password on my win32 box?
(Python i/f next :-)
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 6 19:14:01 2005