Similar to the solution above, this is not future-proof either - you need to apply the svn:ignore property yourself when creating new projects/folders. This is a brute-force approach - it will actually set the svn:ignore on each and every single folder below current folder. Subversion has this feature to set properties recursively, like in svn propset svn:ignore bin -recursive.And when somebody creates a new project, they need to remember to add the svn:ignore property on the new project's folder, and they will forget again and again. This might be hard when you have 191 projects in a solution (you don't? I do! And I don't like it to be clear). First, the svn:ignore property does not work recursively, so setting it just for your solution folder is not helpful at all - you need to set it for each project's folder individually.
NET developer's typical example: ignoring all "bin" and "obj" folders in whole solution's folder hierarchy. inheritable properties and it's a nice little mess to deal with. Throw in some information about recursive properties vs. The good old svn:ignore property and its inheritable (but not recursive!) counterpart, the svn:global-ignores property (Subversion 1.8 only), not to be mistaken for the client-specific global-ignores runtime configuration variable.
0 kommentar(er)
