[MEI-L] @clef* inside scoredef

TW zupftom at googlemail.com
Mon Jul 11 11:22:34 CEST 2011


Sending notifications to the list sounds like a good idea to me.  How
are raised issues managed currently?


2011/7/11 Peter Stadler <stadler at edirom.de>:
> There *must* be a way to automatically send an email when a new ticket is created and the recipient could be MEI-L.
> I'd definitely opt for this approach rather than reporting bugs on the list (alone). Bug tracking is a great help for not forgetting bugs ;-)
> Secondly, in terms of public image it's always good to create some activity on sourceforge...
>
> All the best
> Peter
>
> Am 11.07.2011 um 08:02 schrieb Andrew Hankinson, Mr:
>
>> I think you'll get a better response from the list. Someone might see your message on the bug tracker a couple months from now, but I don't think anyone really looks at it on a daily basis.
>>
>> -Andrew
>>
>> On 2011-07-10, at 3:34 PM, TW wrote:
>>
>>> I'm wondering why the @clef* family of attributes is allowed on
>>> <scoredef>, but the <clef> element isn't.
>>>
>>> Is it O.K. to just drop a message to the list when I believe there are
>>> some inconsistencies in the specs?  I see that the tracker on
>>> Sourceforge hasn't been used yet, but I feel that would be a better
>>> place for posting such things.  Shall I take its virginity?
>>>
>>> Thomas Weber
>>>
>>> _______________________________________________
>>> mei-l mailing list
>>> mei-l at lists.uni-paderborn.de
>>> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>>
>>
>> _______________________________________________
>> mei-l mailing list
>> mei-l at lists.uni-paderborn.de
>> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>
>
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>



More information about the mei-l mailing list