9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] APE select() and awkward Python subprocess PIPEfitting
Date: Tue, 26 Feb 2013 12:25:12 -0600	[thread overview]
Message-ID: <D9648B31-AF2B-4A2A-A601-56656B621C9E@corpus-callosum.com> (raw)
In-Reply-To: <47D4B247-AE2A-4356-9E79-21293DBCE75E@9srv.net>


On Feb 26, 2013, at 10:48 AM, Anthony Sorace <a@9srv.net> wrote:

> I believe that's about the old X11 port. fgb's equis is much newer and nicer (aside from, y'know, X11). That's the one forest against (for anyone who's going to try).


While we're at it, does anyone have an answer to why we have both

	/sys/include/ape/select.h
	/sys/include/ape/sys/select.h

From what I can tell it was a result of the cut being copied
to the new release:

; ls -l select.h sys/select.h
--rw-rw-r-- M 3198 glenda sys 779 Dec 11  1999 select.h
--rw-rw-r-- M 3198 glenda sys 779 Feb 28  2002 sys/select.h


I motion we rm /sys/include/ape/select.h and keep the <sys/select.h>
per most other posix-like systems.

-jas




  reply	other threads:[~2013-02-26 18:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26  2:29 Jeff Sickel
2013-02-26  5:53 ` Jeff Sickel
2013-02-26 11:25 ` Yaroslav
2013-02-26 11:41   ` Charles Forsyth
2013-02-26 16:17     ` Jeff Sickel
2013-02-26 15:29   ` Jeff Sickel
2013-02-26 16:20     ` Charles Forsyth
2013-02-26 16:26       ` Charles Forsyth
2013-02-26 17:01         ` Jeff Sickel
2013-02-26 18:36           ` Charles Forsyth
2013-02-26 16:48     ` Anthony Sorace
2013-02-26 18:25       ` Jeff Sickel [this message]
2013-02-27  2:03     ` Federico G. Benavento
2013-02-27 15:03       ` Jeff Sickel

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=D9648B31-AF2B-4A2A-A601-56656B621C9E@corpus-callosum.com \
    --to=jas@corpus-callosum.com \
    --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).