subclipse - Is it safe to set SVN to ignore . in a directory that should be version controlled? -
yesterday, asked a question why directories can appear subclipse contain uncommitted changes when don't. answer setting svn:ignore
status on pseudo-directory .
counted modification, subclipse didn't show because doesn't deal .
.
knowing cause nice, issue isn't resolved. safe commit addition of ignore status .
pseudo-directory? not want actual directory ignored svn; want make uncommitted change decorator go away. (no, haven't tried doing it. wouldn't know how cleanly revert change if turned out problematic.)
edit:
pointed out in tim's answer, blaming modification of .
misleading. .
marked modified because 1 of subdirectories set svn:ignore
; that's real change , root cause.
based on output of svn diff
received, setting svn:ignore
resource target
. property information saved on parent versioned resource (in case project root .
) can committed repository independent of local ignore settings.
given this, safe commit property change? depends on impact want make. documentation makes note svn:ignore
property:
the svn:ignore property way tell subversion ignore files present in every user's working copy of directory, such compiler output...
so, committing change, you'd effective ignore target
resource pulled project repository (provided it's unversioned). it's possible may not policy @ workplace though, may want avoid this. remove property, can take 1 of following actions:
- run
svn propdel svn:ignore .
command line - in eclipse (with subclipse), right-click project folder, go team -> show properties, select
svn:ignore
property entry, right-click, , click delete property
this should rid of modification notice on root directory. respect previous question, problem have been more apparent had not been fact property changes show normal outgoing changes in synchronization view. if bring commit dialog, should see distinct property change decorator.
unfortunately, leaves target
resource unignored. fix in eclipse, can add target
list of ignored resources. option, go window -> preferences -> team -> ignored resources. can add "target" list of ignore patterns. if wish apply ignore pattern subversion globally, can modify global-ignores
setting of subversion configuration file.
the problem approach ignores target
resource projects in eclipse workspace, or subversion actions across system (depending on ignore method of choice). @ moment, can't think of way reverse on case-by-case basis.
Comments
Post a Comment