[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Exclusions don't work for alias modules
From: |
Stephen Rasku |
Subject: |
Exclusions don't work for alias modules |
Date: |
Thu, 8 Mar 2001 11:11:22 -0800 (PST) |
Tested CVS 1.10.8 on Solaris 7.
I have a module specified, like so:
foo path/to/foo
FOO -a foo !foo/ignore-me1 !foo/ignore-me2
If I check out foo like this:
cvs co FOO
I get foo with ignore-me1 and ignore-me2 excluded. This is as it
should be. However, if I do:
cvs co -d foo1 FOO
The ignore-me[12] directories are included anyways.
Now, if I specify another module like this:
bar another/path/to/bar
FOOBAR foo bar !foo/ignore-me1 !bar/ignore-me3
And I do
cvs co FOOBAR
This works as expected. The files are excluded from their respective
directories. However, if I do:
cvs co -d babar FOOBAR
I only get foo checked out (with a top-level name of babar). I don't
get bar checked out at all. foo also contains the ignore-me1
directory in this case.
I don't know what the solution is for the second case. Using the -d
option in this case can't make sense. I recommend that an error
message be displayed and the checkout should fail.
In the first case, CVS should be smart enough to determine that I have
just renamed the directory from foo to foo1. It would know to exclude
the specified sub-directories from the (newly renamed) directory
causing foo1/ignore-me1 and foo1/ignore-me2 directories to be ignored.
--
Stephen Rasku E-mail: stephen@tgivan.com
Senior Software Engineer Web: http://www.pop-star.net/
TGI Technologies
- Exclusions don't work for alias modules,
Stephen Rasku <=