RE: Getting only directory not files

[Jacob Weber]

Actually, I have a followup question. Say I want to work in a directory with a name other than that of the module (for example, to keep working copies for different branches).

 

I try:

    cvs co -d myDirectoryName -N module/dir/dir/file

but it creates:

    myDirectoryName/module/dir/dir/file

when all I want is:

    myDirectory/dir/dir/file

 

It seems that if I pass just a module name to co, it will use my -d option in place of the module name. But if I send a module name followed by a directory path, it will use my -d option AND the module name. Is there a reason for this, or a way to avoid it?

 

I have to use co (not update), because update won't create the directories if I don't have them already.

 

Thanks,

Jacob

 

-----Original Message-----
From: Jacob Weber [mailto:address@hidden
Sent: Friday, October 21, 2005 3:09 PM
To: Russ Sherk; address@hidden
Subject: RE: Getting only directory not files

Sorry; I was doing 'update', not 'co'.

Jacob

-----Original Message-----
From: Jacob Weber [mailto:address@hidden
Sent: Friday, October 21, 2005 2:53 PM
To: Russ Sherk; address@hidden
Subject: RE: Getting only directory not files

That dosn't seem to work. If I don't have basedir or directory1, it tells me:

    cvs [update aborted]: no such directory `basedir'

Jacob

 

-----Original Message-----
From: address@hidden [mailto:address@hiddenOn Behalf Of Russ Sherk
Sent: Friday, October 21, 2005 2:21 PM
To: Ben Hagenberger
Cc: address@hidden
Subject: Re: Getting only directory not files

Another idea is to apply a tag only to the files you want in the migration package and do a cvs co -rMIG_TAG modulename.  This will only pull down the tagged files (unless you use -f; f=force head revision if tag does not exist on file)

E.g.
cvs rtag -r <rev/tag> MIG_TAG modulename\basedir\directory1\file1
cvs rtag -r <rev/tag> MIG_TAG modulename\basedir\directory2\file2
cvs co -r MIG_REV modulename\basedir\directory1 modulename\basedir\directory2