>> With CVS, I created a branch after each release and used this branch
>> for bugfixes and the trunk for new development. Is this method
>> recommended for subversion as well? And can I assign a sort of
>> symbolic name to this branch so that the branch name itself is
>> different for each release (e.g. "release-030919"),
I guess you didn't read chapter 4, which is all about how to create
branches? :-)
>> but the most recent release is also available as "release"?
Branches and tags are just directories; so the only way to do this is to
copy the latest tag directory to 'release'. Then when a new tag comes out,
delete the 'release' directory, and recreate it as a copy of the latest tag.
You'll have to recreate the 'release' directory every time.
>> Some files are used in more than one project. If I put all these
>> projects into the same repository, is there a way to link these files
>> togehter so that a change to one position of this file is duplicated
>> in all other?
>
> check the book for "svn:externals" about that.
I don't think he's talking about working copies, I think he's talking about
repository changes being replicated via hard-links. And the answer
is "no": at this time, the repository only contains files and directories,
no hard or soft links.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 20 21:32:00 2003