Barry Callahan wrote:
> I've been using zipfiles to make snapshots of my development
> directories. Recently, I've decided maybe a solution that's a little
> more robust might be in order, so I'm looking to migrate to SVN.
>
> I'd like a bit of advice on how to go about doing that. Perhaps even
> just a sanity check.
>
> Using the standard layout, I figured the current source would get
> imported under trunk/ and each snapshot should be unzipped and imported
> as a tag (eg: tags/release_x).
>
> If I understood correctly, unlike, say, RCS, since SVN doesn't version
> individual files, I guess it doesn't matter so much what order things
> get imported in. Right?
>
> If I follow this course of action, would I end up being penalized in
> terms of disk usage or performance over some other, preferred method?
>
> Is the SVN server smart enough to realize that, even if I follow this
> course of action, that
>
> /trunk/foo/bar.c
> /tags/release1/foo/bar.c
> /tags/release2/foo/bar.c
>
> are all the same file with minor (if any) differences?
No, importing separately will preserve your snapshots but svn won't have any
concept of the history of any copy. You should probably look at the
documentation related to 'vendor drops' to see the procedure and tools for
handling snapshots that were made outside of version control so svn understands
their relationships.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2010-06-10 23:51:54 CEST