Hello,

Is it possible to entirely get rid of those painful ecos/images
subdirectory (by moving it into separate module or something)?

The problem is that while it is indeed not checked out on initial
checkout of the 'ecos' module, the next

cvs update -d -P

brings it back into the working tree. Updating without -d is a bad idea
as it doesn't checkout new directories into the working tree when they
appear in the repository.

BTW, is there a way to get entire eCos public CVS *repository* in order
to mirror it locally?

-- Sergei.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Reply via email to