tags versus branches

Hello,

I am trying to decide how best to structure my repository.

I understand the purpose of a tag is to effectively label a snapshot of the
project at a given point in time, and that the purpose of a branch is to
permit development work to continue outside of the trunk area starting at a
selected point in time. I also understand that tags and branches are
essentially equivalent to one another when they are created (using "fast
copies").

However, I do not see why I should bother to create a separate directory in
the repository for TAGS versus BRANCHES. Why not simply have a TRUNK
directory for new development work, and a BRANCHES directory for either tags
or branches? After all the only difference between a tag and a branch is
whether the code is modified after it is created.

Can anyone suggest a reason to bother with a third directory called TAGS? I
appreciate any insights into this that I may have overlooked.

Thanks.

Kirk
Received on 2008-08-01 08:01:00 CEST