= Issues mailto:unicorn-public@bogomips.org is the best place to report bugs, submit patches and/or obtain support after you have searched the {email archives}[http://bogomips.org/unicorn-public/] and {documentation}[http://unicorn.bogomips.org/]. * No subscription will ever be required to email the public inbox. * Cc: all participants in a thread or commit, as subscription is optional * Do not {top post}[http://catb.org/jargon/html/T/top-post.html] in replies * Quote as little as possible of the message you're replying to * Do not send HTML mail or images, it will be flagged as spam * Anonymous and pseudonymous messages will always be welcome. * The email submission port (587) is enabled on the bogomips.org MX: http://bogomips.org/unicorn-public/20141004232241.GA23908@dcvr.yhbt.net/t/ If your issue is of a sensitive nature or you're just shy in public, then feel free to email us privately at mailto:unicorn@bogomips.org instead and your issue will be handled discreetly. If you don't get a response within a few days, we may have forgotten about it so feel free to ask again. == Bugs in related projects unicorn is sometimes affected by bugs in its dependencies. Bugs triggered by unicorn in mainline Ruby, rack, GNU C library (glibc), or the Linux kernel will be reported upstream and fixed. For bugs in Ruby itself, we may forward bugs to https://bugs.ruby-lang.org/ and discuss+fix them on the ruby-core list at mailto:ruby-core@ruby-lang.org Subscription to post is required to ruby-core, unfortunately: mailto:ruby-core-request@ruby-lang.org?subject=subscribe For uncommon bugs in Rack, we may forward bugs to mailto:rack-devel@googlegroups.com and discuss there. Subscription (without any web UI or Google account) is possible via: mailto:rack-devel+subscribe@googlegroups.com Note: not everyone can use the proprietary bug tracker used by Rack, but their mailing list remains operational. Uncommon bugs we encounter in the Linux kernel should be Cc:-ed to the Linux kernel mailing list (LKML) at mailto:linux-kernel@vger.kernel.org and subsystem maintainers such as mailto:netdev@vger.kernel.org (for networking issues). It is expected practice to Cc: anybody involved with any problematic commits (including those in the Signed-off-by: and other trailer lines). No subscription is necessary, and the our mailing list follows the same conventions as LKML for interopability. There is a kernel.org Bugzilla instance, but it is ignored by most developers. Likewise for any rare glibc bugs we might encounter, we should Cc: mailto:libc-alpha@sourceware.org Keep in mind glibc upstream does use Bugzilla for tracking bugs: https://sourceware.org/bugzilla/ == Submitting Patches See the HACKING document (and additionally, the {SubmittingPatches}[https://git.kernel.org/cgit/git/git.git/tree/Documentation/SubmittingPatches] document distributed with git) on guidelines for patch submission. == Contact Info * public: mailto:unicorn-public@bogomips.org * private: mailto:unicorn@bogomips.org * nntp://news.gmane.org/gmane.comp.lang.ruby.unicorn.general * nntp://news.public-inbox.org/inbox.comp.lang.ruby.unicorn * http://bogomips.org/unicorn-public/ We operate a {public-inbox}[http://public-inbox.org/] which feeds the mailing list. Subscription is optional, so Cc: all participants. You can follow along via NNTP: nntp://news.public-inbox.org/inbox.comp.lang.ruby.unicorn nntp://news.gmane.org/gmane.comp.lang.ruby.unicorn.general Or Atom feeds: http://bogomips.org/unicorn-public/new.atom The HTML archives at http://bogomips.org/unicorn-public/ also has links to per-thread Atom feeds and downloadable mboxes. You may also subscribe via plain-text email: mailto:unicorn-public+subscribe@bogomips.org (and confirming the auto-reply)