From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] libmemlayer bug
Date: Mon, 9 Dec 2013 01:41:48 -0500 [thread overview]
Message-ID: <d32e429baa9f831c3499136748fa7279@mikro> (raw)
In-Reply-To: <55dbceb34c7d3f45100fd9cbf396b510@felloff.net>
> in 9front, i added drawclipnorepl() function that is like drawclip() but does not clamp
> the source and mask rectangles to be in src->r and mask->r and use it in libmemlayer.
why can't you fix the existing function?
- erik
next prev parent reply other threads:[~2013-12-09 6:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 4:09 cinap_lenrek
2013-12-09 4:43 ` Conor Williams
2013-12-09 5:00 ` cinap_lenrek
2013-12-09 5:28 ` Conor Williams
2013-12-09 6:09 ` Matthew Veety
2013-12-09 6:22 ` Conor Williams
2013-12-09 6:26 ` erik quanstrom
2013-12-09 13:05 ` Matthew Veety
2013-12-09 6:41 ` erik quanstrom [this message]
2013-12-09 6:54 ` cinap_lenrek
2014-01-15 6:06 ` Conor Williams
2014-01-15 7:52 ` cinap_lenrek
2014-01-15 8:30 ` Conor Williams
2014-01-15 14:42 ` erik quanstrom
2014-01-15 19:08 ` cinap_lenrek
2014-01-15 21:19 ` Conor Williams
2014-01-15 21:31 ` Conor Williams
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=d32e429baa9f831c3499136748fa7279@mikro \
--to=quanstro@quanstro.net \
--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).