Mailing List Archive

I just read a blog post and thought that might be the alternative solution to migrate all issues into the webserver issues:
https://github.com/blog/1439-closing-issues-across-repositories

I also thought about omitting invalids and duplicates.

any thoughts?



________________________________
Von: "cherokee@googlecode.com" <cherokee@googlecode.com>
An: cherokee-dev@cherokee-project.com
Gesendet: 17:06 Dienstag, 19.März 2013
Betreff: [Cherokee-dev] Issue 1397 in cherokee: +++ PLEASE READ – ISSUES ARE MOVING TO GITHUB – PLEASE READ +++

Status: New
Owner: ----

New issue 1397 by psaod8fz...@gmail.com: +++ PLEASE READ – ISSUES ARE MOVING TO GITHUB  – PLEASE READ +++
http://code.google.com/p/cherokee/issues/detail?id=1397

In the next couple of days we are moving the issues to Github.


    ***************************************************************
    *                                                            *
    *    If you found a bug, please leave open an issue at:      *
    *        https://github.com/cherokee/webserver/issues        *
    *                                                            *
    *    Please do NOT create new issues in this issue tracker    *
    *                                                            *
    ***************************************************************

--You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev