From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] duppage
Date: Sat, 3 Mar 2012 20:30:59 +0100 [thread overview]
Message-ID: <7ca391fa0b9cf1b3b72fb100981732a4@gmx.de> (raw)
In-Reply-To: <3856aed1f3999b912c4f9d74fd19356f@hamnavoe.com>
> Jetzt verstehe ich. Before returning 1 (failure) duppage
> always calls uncachepage first, so no harm is done.
exactly!
> How about submitting a patch(1)?
i think geoff is working on it.
i wanted to verify this first. the code is subtile and
there might be even better ways to fix this.
modified the pager and swap code in 9front in other ways
too. so making a patch for sources plan9 requires me do
do some manual recreation of the fix and bind fakery.
--
cinap
next prev parent reply other threads:[~2012-03-03 19:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 3:29 cinap_lenrek
2012-02-25 20:09 ` Charles Forsyth
2012-02-26 4:13 ` erik quanstrom
2012-02-29 10:31 ` Richard Miller
2012-02-29 14:14 ` cinap_lenrek
2012-02-29 19:35 ` Richard Miller
2012-02-29 19:50 ` cinap_lenrek
2012-03-03 9:58 ` Richard Miller
2012-03-03 19:30 ` cinap_lenrek [this message]
2012-03-13 23:55 erik quanstrom
2014-06-08 14:53 erik quanstrom
2014-06-08 17:15 ` cinap_lenrek
2014-06-08 17:22 ` Charles Forsyth
2014-06-08 17:34 ` erik quanstrom
2014-06-08 17:50 ` Charles Forsyth
2014-06-08 17:53 ` erik quanstrom
2014-06-08 17:54 ` cinap_lenrek
2014-06-08 18:15 ` erik quanstrom
2014-06-08 18:37 ` Charles Forsyth
2014-06-09 8:23 ` Charles Forsyth
2014-06-09 13:21 ` erik quanstrom
2014-06-10 1:35 ` erik quanstrom
2014-06-10 3:53 ` cinap_lenrek
2014-06-10 12:58 ` erik quanstrom
2014-06-10 13:56 ` Steve Simon
2014-06-10 15:30 ` erik quanstrom
2014-06-10 14:06 ` cinap_lenrek
2014-06-11 18:04 ` erik quanstrom
2014-06-08 17:49 ` cinap_lenrek
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=7ca391fa0b9cf1b3b72fb100981732a4@gmx.de \
--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).