I don't know how you implemented .cvsignore, but why
not use cvs to know which files have been added ? I
often use:
cvs -Q -n update | grep '^\?' | cut -f2 -d' '
That's a good question. By not using cvs itself to see what
files have been added, it eliminates the call to the cvs
server. So if you run "cvsdelta --nodiff" (to not do the
"cvs diff"), you can see the added and removed files without
having to connect to the server at all, which is useful for
when you have no connection or a slow one, or when you just
don't want to be typing your password every time.
If the $CVSROOT/CVSROOT/cvsignore file exists locally, then
it would be simple to read that file as well. It is
uncertain what could be done if the server is remote.
I'll consider adding an option so that cvs is used for
generating the added files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=316860
That's a good question. By not using cvs itself to see what
files have been added, it eliminates the call to the cvs
server. So if you run "cvsdelta --nodiff" (to not do the
"cvs diff"), you can see the added and removed files without
having to connect to the server at all, which is useful for
when you have no connection or a slow one, or when you just
don't want to be typing your password every time.
If the $CVSROOT/CVSROOT/cvsignore file exists locally, then
it would be simple to read that file as well. It is
uncertain what could be done if the server is remote.
I'll consider adding an option so that cvs is used for
generating the added files.