This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
I sympathize with your request. However, we should note that those of us not
using subversion for our work (e.g., using Hg or GIT) may not see this
problem despite best intentions. Those system set "ignore" on a global
basis, not on a per directory basis like svn. So (a) we just don't see any
warning about this, and (b) we don't have a way to set those properties in
When we merge the work from our repository over to an svn checkout, we
typically do not build it there. This helps when we are transitioning back
and forth between the official svn repository and our local repository. So
we again won't see an svn:ignore issue.
I know that doesn't help any, but I think it probably explains the majority
of what you are seeing. I'm not sure there is a good answer, unfortunately.
On 2/12/08 7:46 AM, "Jeff Squyres" <jsquyres_at_[hidden]> wrote:
> Developers --
> When you add a new component, framework, or anything that includes one
> or more new directories: please be sure to set the svn:ignore property
> on each new directory properly. Here's the SVN docs on the svn:ignore
> It is proper to ignore all automatically-generated files, such as (but
> not limited to):