Is it safe to set SVN to ignore. in the directory that should be version controlled?

Question

Yesterday I asked a question about why directories might appear in Subclipse to contain uncommitted changes when they actually don't. The answer was that setting the svn:ignorestatus in the pseudo .-directory was considered a modification, but Subclipse did not show anything, since it has nothing to do with ..

Knowing the reason is good, but the problem is not completely resolved. Is it safe to commit ignoring status to pseudo-directory .? I do not want the actual directory to be ignored by SVN; I just want the decorated change decoder to disappear. (No, I did not try to just do this. I would not know how to undo the change cleanly if this turned out to be problematic.)

EDIT:
As Tim’s answer stated, the charge of modification .is misleading. .was only marked as modified because one of the subdirectories was set to svn:ignore; that the real change and the root cause.

Answer 1

svn diff, , svn:ignore target. ( .), .

, ? , . svn:ignore:

svn: ignore - Subversion , , ...

, , target , ( , ). , , . , :

• svn propdel svn:ignore .
• Eclipse ( Subclipse) , " → ", svn:ignore, " "

. , , , "". Commit, Property Change.

, target. Eclipse, target . , "" → "" → "" → " ". "" . Subversion , global-ignores Subversion.

, target Eclipse Subversion ( ). .