> I'm not quite sure if you really understand the impact of svn:ignore.
> What behaviour are you expecting from the svn:ignore mechanism exactly,
> and how would the expected behaviour impact your workflow?
We want the unversioned files to not show in svn status or in
tortoiseSVN's "Add" command w
> Is editing the global-ignores setting in the Subversion configuration file,
> as already suggested by Thorsten in an earlier post, not an option?
>
> That's currently the only unversioned place where ignore settings can
> be configured. See
> http://svnbook.red-bean.com/en/1.7/svn.advanced.confa
> Just to be clear: What you call your build system is used directly by
> the devs and something we can think of as some kind of assistant to
> get pre configured working copies, right? The devs start this
> assistant, choose whatever fits their need and afterwards it is
> checking out, setting up
> I don't think I did fully understand the interaction between your
> build system and your devs, as normally build systems like Jenkins,
> Hudson etc. run on a separate server fully automated and per default
> just don't commit anything, therefore it's very unimportant if the
> working copy they a
Hello all,
I have searched for this issue in several places, but none of the
feature requesters presented a scenario like mine, and the overall
conclusion was that the svn:ignore property was sufficient. However, I
stand by the opinion that a local .svnignore file is also necessary
(or some ki
