Multiple Fisheye repos pointing to same location wasting space?

[Doug Strick]

We're running an older Fisheye 3.10 instance.  I'm not very familiar with how the product works, but upon looking through the configured repos I'm seeing multiples with different names pointing at the same location.  An example is 2 repos pointing at perforce:1666//projectA/folder1. 

• The SCM Details section are configured exactly the same
• Include/Exclude Paths are different

Does it make sense to have different repos pointing at the same location, but different exclusions?  If the same locations exist among the exclusion configs does that waste disk space?  I've got another user wanting a new repo created pointing to the same root so I'm trying to determine if we can reuse anything.  Thanks

[Ben Stuart]

Hey Doug, 

It just depends on if each repository is indexing certain locations or file types exclusively. I can't think of a good reason that you would want to have 2 repositories that are mostly the same. Maybe you can get some more details from your users about that.