提交 2009983c authored 作者: Thomas Mueller's avatar Thomas Mueller

--no commit message

--no commit message
上级 a59e0765
Tips for email contributors
* Feature requests are always welcome, even if the feature is already on the roadmap.
Your mail will help prioritize feature requests.
If you urgently need a feature, consider providing a patch.
* Bugs: include the complete error message and stack trace, including the root cause stack traces.
* Sending source code: to avoid formatting problems, consider using a public web clipboard
http://pastebin.com
http://cl1p.net
http://www.mysticpaste.com/new
* For large attachments, use a public...
* Issue tracking versus emails:
You don't need to create issue reports, sending an email to the group is enough.
If you want, you can create an issue.
* Keep your test cases and email as short as possible.
Specially when creating test cases, please keep the code as simple and short as possible,
but so that the problem can still be reproduced.
Method that simply call other methods should be avoided,
as well as unnecessary exception handling.
* It may take a few days to get your answers.
-----------------
Benchmark:
Hi,
......
......@@ -620,3 +620,6 @@ imageio argb bilinear rendering stroke interpolation flip diagrams draw
delim overlap subselect bitwise dclassifier dgenerate compacts chartrand phane
sval cement slave ulimit eclipselink glenn kidd rapidshare score relevance
autovacuum vacuuming endlessly talking evicted splitting unbound declaring
selector descendant isdescendantnode issamenode ischildnode localname
weakreference ancestor junctions wake fills rail sleeps turns grammars straight
answers attachments emails clipboard prioritize tips urgently standby
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论