On Sep 6, 2005, at 16:49, Dave Pawson wrote:
> Sorry Ryan. I'm either not following you or it isn't making sense.
> I tried another tack which *seems* to work.
> I have a 'working copy' (directory created when I checked out the
> directory (contains tags, trunk and branches)
> cd to that directory
>> cd <wkingDir>
> copy any old file into the trunk directory.
>> copy /temp/trash.txt /trunk
>> svn st
> shows me that svn has a foreigner on board ;-)
> ? trunk/trash.txt
>> svn add trunk/trash.txt
> Now commit
>> commit -m "test file, trash.txt"
> this seems to work OK, and makes sense to me (OK OK :-)
> Is that a reasonable way of introducing new files?
Sorry if I wasn't clear earlier, but yes, what you've described above
is exactly how you do things in Subversion.
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.
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". 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) 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.
I'm surprised you had trouble after reading the book.... It was all
fairly clear to me after I read it, and I had no background in
version control. 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.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Sep 6 18:56:08 2005