On Tue, Sep 11, 2012 at 9:38 AM, John Maher <JohnM_at_rotair.com> wrote:
> Thanks Mark!!! That might be exactly what I was looking for. Now I
> have an unusual question I don’t know if anyone knows the answer. I may
> just try it anyway. What happens if I have more ignores than I need. Will
> it hurt performance much? For example, my setup looks like this:****
> ** **
> Reporitory/Project1/My Project****
If this were me, I would have an svn:ignore on my Project1 folder that
ignores the bin and obj folder. That would cause everything inside those
folders to also be ignored.
For other folders, I could then add specific file patterns only if needed.
Odds are I would have all my build output in bin and obj though so probably
not a lot else to ignore.
What if I set this property recursively “svn:ignore *.sou *proj.user bin
> obj”? I know it will get applied to many directories unnecessarily.
I do not think it will cause any performance issues at all. That said, it
seems like those ignores would only need to be applied on the project root
folder. If you have bin and obj folders being created all over the place
it seems like you ought to fix that.
> For example, only the top level directory (Project1) will contain any
> *.sou files. The ignore will get applied everywhere, even where it is not
> needed. Can this cause any major issues?
> I like the idea of entering the property once. Although I can go down
> the line and paste the property where it is supposed to go. Is it worth
> the extra effort?
Setting svn:ignore is pretty much a one-time deal. That is why you are not
going to find many tools to automate. There is no payoff in spending the
time to write such a tool. I personally do not like seeing the property
set where it is not needed or with values that are not needed. It does not
cause performance problems, it just adds "noise". I do not believe
manually setting up the property is a lot of work. Even if it is 44
projects. I would just set it up and deal with it as needed.
Received on 2012-09-11 15:47:57 CEST