Koushik,
This was done to avoid duplicate e-mails, notifications and item tracking checks when you want to configure both a parent and a child SVN directory. Lets say you want to apply more stringent commit rules to "branches/newbranch", but just some general rules to the parent "branches". In both cases, you want the same list of users to get notification. Without the precidence check, you would get 2 e-mails for the same commit.
As it currently sits, you can't disable this check. I can easily make it configurable if you want me to.
Just let know,
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No. Its cool. I used generic condition to check that some log message was entered but it didnt work (though it did previous version). Precidence check is the better way to go!
Cheers,
Koushik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
[6/13/2008 11:45:33 AM] SetRepoPathPrecidence :: Incomming configs = 3 ; Returning configs = 1
[6/13/2008 11:45:33 AM] SelectApplicableReproConfigs :: Returning 1 RepoPathConfig objects
When more configs are applicable only one of them is selected. Why is this so? Can it be disabled?
This is NOT an issue - just curious as to why this was done.
Cheers
Koushik
Koushik,
This was done to avoid duplicate e-mails, notifications and item tracking checks when you want to configure both a parent and a child SVN directory. Lets say you want to apply more stringent commit rules to "branches/newbranch", but just some general rules to the parent "branches". In both cases, you want the same list of users to get notification. Without the precidence check, you would get 2 e-mails for the same commit.
As it currently sits, you can't disable this check. I can easily make it configurable if you want me to.
Just let know,
Mike
Mike,
No. Its cool. I used generic condition to check that some log message was entered but it didnt work (though it did previous version). Precidence check is the better way to go!
Cheers,
Koushik