The subject below was created by a mail sent out by Trac. With both trac and mailman generating header prefixes, there remains little to be seen in the subject line summary about the real subject.
I'd like to request the default config to be tweaked so that Trac doesn't generate a Subject prefix. (I probably can change the cl-irc and usocket setups myself...)
bye,
Erik.
(The message:)
#13: Add SEEN and SPOKE support -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: pre-1.0 Component: chat | Version: Keywords: | Has_patch: 0 -------------------------+-------------------------------------------------- Or, more generally speaking, add functionality to track any requested message type, possibly on a per-user basis.
The functionality should also support persistence.
-- Ticket URL: http://trac.common-lisp.net/cl-irc/ticket/13 cl-irc http://common-lisp.net/project/cl-irc cl-irc
-- "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
_______________________________________________ cl-irc-ticket mailing list cl-irc-ticket@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cl-irc-ticket
On 5/6/06, Erik Huelsmann ehuels@gmail.com wrote:
I'd like to request the default config to be tweaked so that Trac doesn't generate a Subject prefix. (I probably can change the cl-irc and usocket setups myself...)
A valid request. Unfortunately it would involve a patch to the Trac source. If you feel strongly about it I will maintain such a patch but if it can be avoided I'd rather not. Let me know. :-)
Erik.
On 5/8/06, Erik Enge erik.enge@gmail.com wrote:
On 5/6/06, Erik Huelsmann ehuels@gmail.com wrote:
I'd like to request the default config to be tweaked so that Trac doesn't generate a Subject prefix. (I probably can change the cl-irc and usocket setups myself...)
A valid request. Unfortunately it would involve a patch to the Trac source. If you feel strongly about it I will maintain such a patch but if it can be avoided I'd rather not. Let me know. :-)
Should I create a patch and submit it with the Trac people (in order to make it available in newer releases)?
Bye,
Erik.
On 5/8/06, Erik Huelsmann ehuels@gmail.com wrote:
Should I create a patch and submit it with the Trac people (in order to make it available in newer releases)?
If you would create a patch I'll happily apply it even more so if you submit it back with the Trac guys to make this configurable.
Thanks! Erik.
-
Erik Enge -
Erik Huelsmann