Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

102 lines (77 sloc) 4.08 KB
= Issues is the best place to report bugs,
submit patches and/or obtain support after you have searched the
{email archives}[] and
* 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}[] in replies
* Quote as little as possible of the message you're replying to
* Do not send HTML mail, it will be flagged as spam
* Anonymous and pseudonymous messages will always be welcome.
If your issue is of a sensitive nature or you're just shy in public,
then feel free to email us privately at
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 and discuss+fix them on the ruby-core
list at
Subscription to post is required to ruby-core, unfortunately:
For uncommon bugs in Rack, we may forward bugs to and discuss there.
Subscription (without any web UI or Google account) is possible via:
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
and subsystem maintainers such as
(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 Bugzilla instance, but it is
ignored by most developers.
Likewise for any rare glibc bugs we might encounter, we should Cc:
Keep in mind glibc upstream does use Bugzilla for tracking bugs:
== Submitting Patches
See the HACKING document (and additionally, the
document distributed with git) on guidelines for patch submission.
== Contact Info
* public:
* private:
We operate a {public-inbox}[] which
feeds the mailing list. You may subscribe either using
{ssoma}[] or by sending a mail
ssoma is a mail archiver/fetcher using git. It operates in a similar
fashion to tools such as slrnpull, fetchmail, or getmail. ssoma
subscription instructions:
# to initialize a maildir (this may be a new or existing maildir,
# ssoma will not touch existing messages)
# If you prefer mbox, use mbox:/path/to/mbox as the last argument
# You may also use imap://$MAILSERVER/INBOX for an IMAP account
# or imaps:// for an IMAPS account, as well.
ssoma add $LISTNAME $URL maildir:/path/to/maildir
# read with your favorite MUA (only using mutt as an example)
mutt -f /path/to/maildir # (or /path/to/mbox)
# to keep your mbox or maildir up-to-date, periodically run the following:
ssoma sync $LISTNAME
# your MUA may modify and delete messages from the maildir or mbox,
# this does not affect ssoma functionality at all
# to sync all your ssoma subscriptions
ssoma sync
# You may wish to sync in your cronjob
ssoma sync --cron
HTML archives are available here:
Jump to Line
Something went wrong with that request. Please try again.