From: Russ Cox <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] patch(1)
Date: Thu, 18 Mar 2004 08:38:01 -0500 [thread overview]
Message-ID: <4059A639.1030107@swtch.com> (raw)
In-Reply-To: <042a01c40ce8$fb7cc2a0$8ed97d50@SOMA>
boyd, rounin wrote:
>>just once, it would be nice if you actually understood what was being
>>said before you started spouting off criticizing it. see
>>http://plan9.bell-labs.com/magic/man2html/1/patch,
>>
>>
>
>i stand corrected (actually i'm seated).
>
>
>
>>which has been posted here before.
>>it's not what you think.
>>
>>
>
>fix replica/* and i might be amused.
>
> http://www.cs.bell-labs.com/magic/man2html/1/replica
>
>
what's wrong with them?
next prev parent reply other threads:[~2004-03-18 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 18:47 Russ Cox
2004-03-18 7:41 ` boyd, rounin
2004-03-18 12:37 ` Russ Cox
2004-03-18 13:00 ` boyd, rounin
2004-03-18 13:38 ` Russ Cox [this message]
2004-03-18 14:05 ` boyd, rounin
2004-03-18 17:06 ` Russ Cox
2004-03-18 20:38 ` boyd, rounin
2004-03-18 14:45 ozan s. yigit
2004-03-18 20:09 ` boyd, rounin
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=4059A639.1030107@swtch.com \
--to=rsc@swtch.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).