Ryan Schmidt wrote:
> On May 9, 2007, at 22:37, H.S. wrote:
>> If you can give some other pointers regarding creating the new
>> repositories (I checked the red book, it talks about the directory
>> structure but doesn't give an example showing exactly what to commit
>> while creating the repo), that would be an added bonus.
>
> What else would you like to know? I think you've pretty much covered it
> here.
Assume a project is underway and a few, say 3, programmers are working
on the same set of source code files. (I have used CVS before, but only
for myself and only in a very basic manner). Just to clarify what you
explained earlier, they do:
$> svn checkout svn+ssh://svn.server.somewhere/path/to/project/trunk
the above will create a "trunk" directory in the directory they execute
the command. They will work on their source code then
$> svn commit
and write a comment. That will commit their changes to the "trunk"
directory in the project tree, right?
Next, lets say that the project is in a state that the version at the
time is a "release", source code to be given to anyone else. That
"release" is created by tagging that working version in trunk directory?
Finally, lets say two programmers want to work on newly checked out
version but each of their changes are some major changes. So they can
make a branch from themselves, work on that branch and commit back their
changes into their own branches, and then some time later "merge" those
branches back into the trunk?
Thanks for your earlier explanations,
->HS
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 14:51:04 2007