9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] the futility of #plan9 on irc
Date: Mon, 23 May 2005 07:27:30 -0400	[thread overview]
Message-ID: <ee9e417a05052304277b393581@mail.gmail.com> (raw)

it's like arguing with toothpaste.

exhibit a:

% cd /sys/src/libc/fmt; yesterday -d -0512 .
diff -n /n/dump/2005/0512/sys/src/libc/fmt /sys/src/libc/fmt
diff -n /n/dump/2005/0512/sys/src/libc/fmt/dofmt.c /sys/src/libc/fmt/dofmt.c
/n/dump/2005/0512/sys/src/libc/fmt/dofmt.c:315 a /sys/src/libc/fmt/dofmt.c:316
> 	uintptr pu;
/n/dump/2005/0512/sys/src/libc/fmt/dofmt.c:324 c
/sys/src/libc/fmt/dofmt.c:325,330
< 		u = (ulong)va_arg(f->args, void*);
---
> 		pu = va_arg(f->args, uintptr);
> 		if(sizeof(uintptr) == sizeof(uvlong)){
> 			vu = pu;
> 			isv = 1;
> 		}else
> 			u = pu;
% 

exhibit b:

On 5/14/05, 9trouble@plan9.bell-labs.com <9trouble@plan9.bell-labs.com> wrote:
> 1. <u.h> now includes a definition for uintptr, which we define
> to be an integer of the same width as a pointer.  Pointers and
> uintptrs should be printed using %p.

exhibit c: (weekend irc log for #plan9)

Major-Wi  :yup
          :seems like jmk has btoken fmtinstall()
          :as well

...

uriel     :oh, I fucking love it, latest changes to fmt stuff
          are by jmk, without comments, of course, so who knows
          what the fuck he did! marvelous

noselasd  :history/diff :-)

uriel     :noselasd: yes, but _why_

Major-Wi  :what a bitch
          :i know what jmk did
          :he added reentrancy for threads

uriel     :Major-Willard: 'fuck up'?
          :Major-Willard: oh, reentancy for threads?! Oh holy
          dear mother!


             reply	other threads:[~2005-05-23 11:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 11:27 Russ Cox [this message]
2005-05-23 12:18 ` Vester Thacker
2005-05-23 17:44   ` Bruce Ellis
2005-05-23 17:46     ` Rob Pike
2005-05-23 18:43       ` Tim Newsham
2005-05-24  4:41     ` Dan Cross
2005-05-23 12:22 ` Uriel
2005-05-23 15:55   ` jmk
2005-05-24  0:54   ` Country Joe
2005-05-23 23:33 ` Chris Collins
2005-05-23 23:57   ` andrey mirtchovski
2005-05-24  0:03     ` Eric Van Hensbergen
2005-05-24  0:12       ` andrey mirtchovski
2005-05-24  4:29       ` Tim Newsham
2005-05-24 15:19         ` Russ Cox
2005-05-24 16:39           ` Vester Thacker
2005-05-24 16:43             ` William Josephson
2005-05-24 17:08               ` Vester Thacker
2005-05-26  4:02               ` McLone
2005-06-19 11:41             ` Vester Thacker
2005-06-19 11:43               ` Vester Thacker
2005-05-24 21:07           ` Chris Collins
2005-05-24 21:18             ` Russ Cox
2005-05-25 16:42               ` David Leimbach
2005-05-25 16:58                 ` Bruce Ellis
2005-05-26  9:17                 ` Abhey Shah
2005-05-24 21:20             ` Dan Cross
2005-05-24 21:31               ` Jack Johnson
2005-05-24 21:54                 ` Devon H. O'Dell
2005-05-26  4:04               ` McLone
2005-05-26  4:19                 ` Devon H. O'Dell
2005-05-26  4:29                 ` Dan Cross
2005-05-24  4:46       ` Dan Cross
2005-05-24  5:29         ` Lucio De Re
2005-05-24  0:14   ` Skip Tavakkolian

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=ee9e417a05052304277b393581@mail.gmail.com \
    --to=russcox@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).