At 9:33 Uhr -0500 21.03.2002, Benjamin Reed wrote:
>Steven Burr [[EMAIL PROTECTED]] wrote:
>>  I'd like to make sure I avoid this problem in the future, so I have a
>>  question for the group.  Once SourceForge support removes the directory
>>  from the repository, can I safely commit in the future without first
>>  moving build out of the Project Builder folder? My (obviously limited)
>>  understanding is that a file or directory not already in a cvs
>>  repository needs to be put there with the "add" command before it will
>>  be included in future commits.
>
>It should be safe to commit... when you update you should get a '?' before
>the build directory.  If you want to be more permanent about it, make a
>.cvsignore file with only the line:
>
>build
>
>...in it, in the top-level directory, and check that in.  CVS will ignore
>that directory from then on, if it exists locally.


There is one caveat, though: your local "build" directory now has CVS 
subfolders in it. My suggestion is to trash your local build 
directory (this is harmless, and similiar to the effect of "Clean 
All". But this is mostly of concern if you also want to use CVS from 
the command line.


Max
-- 
-----------------------------------------------
Max Horn
Software Developer

email: <mailto:[EMAIL PROTECTED]>
phone: (+49) 6151-494890

_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to