Eugene Voytitsky <email@example.com> writes:
> Yes, I know 2 ways to specify ignores for SVN:
> 1. (server-side, global) by setting `svn:ignore` property for dir
> 2. (client-side, global) by editing %APPDATA%\Subversion\config
> `global-ignores` property of [miscellany] section
> And I even read the discussion
> Essence of the discussion is:
> "Everything you'd put into a .cvsignore can be put into the svn:ignore
> property with the same results."
> But I don't agree that result is absolutely the same.
> Each of 2 possible SVN ways have disadvantages:
> 1-st way (server-side, global) may be useless when each team member has
> its own stuffs to ignore. Obviously that letting each member ability
> to edit/commit svn:ignore prop will lead to mess in repository soon.
I don't know why you call this "server-side". The situation you
describe here is exactly the functionality .cvsignore files provide.
> 2-nd way (client-side, global) is useless because of global leads to
> inconvenience: I should specify all ignores for all my repositories
> in single config file. Besides of inconvenience it may be also
> impossible to apply the same ignore rules for all repositories.
> .svnignore file support solves all disadvantages mentioned above.
I'm not following this. Could you describe in one sentence an
'ignore' feature you get with CVS that you don't get with Subversion?
An example would help a lot here.
> I have tried to open enhancement issue about this topic
> but the issue had been marked as invalid immediatelly. :(
It was marked as invalid because we prefer to discuss issues here
before filing them. See http://subversion.tigris.org/project_issues.html
for why. It's nothing personal.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Dec 8 07:51:32 2004