"martin de lange" wrote
> Would the trunk be the root directory?
Have you read the help file? It explains the various directory structures
you can use and gives some hints on how to choose the best one for you. That
much is in the RC2 help file at least.
> Do you know why it does not just copy in the folder hierarchy?
It *does* copy the hierarchy, it just doesn't include the top level folder.
If have this structure on your hard drive:
and you right click on Project1 and import into /path/to/repos/trunk/Proj1
you will get in your repository:
> I am an embedded developer so this is not typically my forte.
So am I. Believe me, once you see how it works it really is very easy.
Deciding how you want to organise your repository is worth a bit of thought,
but that applies to any RCS.
I suggest you try a few more experiments with temp repositories. Copy your
source tree to a temp folder and import it and you will see the hierarchy
mirrored in the repository.
> it is a nightmare when one is preocupied with other code matters.
Hmm, I would not want to think about entering something into *any* RCS in
the middle of a crisis. You do need a quiet patch to get it sorted out to
your liking. Once you have your source tree under control, day-to-day use is
> No wonder you get paranoi.
I am not paranoid because of TSVN. I just don't like deleting anything until
I am really, really sure I won't need it. When you place your code under RSC
(any RCS) you only version the source. So there are lots of files (like
object files) which you don't version. The worry is about human error - did
I miss out something when I decided which files should be versioned. That is
why I make sure a fresh checkout into a clean directory will build (and
generate the same hex file, etc) before I dispose of the original.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Sep 29 14:41:07 2004