Hello Thorsten, What happens here is that we have a module with base classes, and all other classes inherit from one in this module. Sometimes we alter something on one of these classes that cause an impact on the subclasses, forcing us to also commit them.
Commiting the modules separately is definitely an easy solution, I just wanted to check if there was some other way to do it. Thank you all for your help. Ricardo -----Mensagem original----- De: Thorsten Schöning [mailto:tschoen...@am-soft.de] Enviada em: terça-feira, 17 de maio de 2011 03:47 Para: users@ Assunto: Re: RES: Blank log messages when user has no access to specific folder Guten Tag Ricardo Smania (Desenv), am Montag, 16. Mai 2011 um 18:36 schrieben Sie: > The path isn't > important, so if there is a way to show the paths and log message, > but without showing the contents, that would also be a viable solution for us. I don't think so, there is only read write access in general, not divided by log, file contents etc. Is there any reason why it's necessary to commit to both of your example modules in one commit and not two? I have the same problem, different tags for different customers with different access rights, and the easiest way to let each customer get his log message is different commits. Of course it's on to the committer to have that in mind, but using a pre commit hook you even may check that there's no commit for both modules with different access rights. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig Telefon: Potsdam: 0331-743881-0 E-Mail: tschoen...@am-soft.de Web: http://www.am-soft.de AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
