Dave Thompson wrote:
Linus Tolke wrote:
Not currently. It is probably possible to set up a mailing list
dispatcher function that does this by receiving each mail and doing
some ingenious filtering.
Is there not an option to have an 'owner' assigned to each subsystem?
If so, that 'owner's' email address could be set to the issues mailing
list for that project.
Could you, before we proceed in this, try to get an idea of how this
is going to affect the current projects. How many projects have
issues in their issuezilla that would then be moved and the persons
working in those projects, how do they feel about this?
To avoid making things worse we should go through all projects that
haven't got any issues in their issuezilla and make sure the issues
link in the project_tools point to the ArgoUML issuezilla and that it
is appearant what subcomponent should be used.
I will take a look.
Dave
Hi Dave,
I'll save you some effort in what regards argouml-cpp...
In argouml-cpp we're using its issue db and we're happy about it (at
least I am).
It is better if you have a specific interest in ArgoUML to have a
specific sub-project, with a specific repository and a specific issue db.
I won't argue the pos and cons besides the above sentence.
Regards,
Luis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
