From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] devdraw.c
Date: Fri, 26 Oct 2012 22:20:36 +0200 [thread overview]
Message-ID: <bd04b4333cfc872825d467f5d57f78dd@rei2.9hal> (raw)
In-Reply-To: <4EB96ED9-A826-495D-9A69-08161C314577@corpus-callosum.com>
yep. thats a bug. good catch!
--
cinap
prev parent reply other threads:[~2012-10-26 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 18:10 Jeff Sickel
2012-10-26 20:20 ` cinap_lenrek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd04b4333cfc872825d467f5d57f78dd@rei2.9hal \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).