On Nov 29, 2004, at 11:53 AM, trlists@clayst.com wrote:
> OK, I am slowly ... very slowly ... getting my head around the
> "Subversion way".
>
> My particular concern at the moment is understanding (a) when commands
> affect the repository, the working copy, or both, and (b) what I can do
> using standard file management commands in the working copy without
> confusing Subversion. I know the former is documented but it is very
> confusing at first. The latter I can't find -- is it discussed
> somewhere? If not can someone explain it?
Does this section not make it clear?
http://svnbook.red-bean.com/en/1.1/ch03s05.html#svn-ch-3-sect-4.2
"File changes
This is the simplest sort of change. You don't need to tell Subversion
that you intend to change a file; just make your changes. Subversion
will be able to automatically detect which files have been changed.
Tree changes
You can ask Subversion to “mark” files and directories for scheduled
removal, addition, copying, or moving. While these changes may take
place immediately in your working copy, no additions or removals will
happen in the repository until you commit them."
Perhaps we need a sentence that says something like: "You MAY NOT
manipulate your working copy with standard file management commands;
you MUST use Subversion to manipulate your working copy. The only
exception to this is changing file contents, which can be done with
your editor, without having to notify Subversion."
?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 29 19:39:50 2004