I've got an environment where I'm checking out d.o contribs via CVS and then check them into a company SVN repository. When code is ready for deployment it is exported from SVN and then deployed via rsync with the C flag on so that CVS folders are ignored.
The problem I saw today was that after grabbing wysiwyg out of CVS and adding the tinymce folder, then checking that into SVN and deploying via rsync I noticed that the tinymce folder was not synced. This is because running rsync with the C flag ignores files in the same way that CVS would ignore files, and respects the tinymce* line in .cvsignore.
I know this is easy enough to get around on my end, but it essentially means that I have to fork the module (however small) in order to use it in my environment.
So, that is why I ask the question in the first place...but is it truly needed to commit .cvsignore files to a project?
Comments
Comment #1
sunHelp me fix #320562: Libraries API and this issue is resolved. ;)