9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: YAMANASHI Takeshi <uncover@campus.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] install libtcs
Date: Fri,  2 Mar 2001 14:13:17 +0900	[thread overview]
Message-ID: <16342.983509997@beat.cc.titech.ac.jp> (raw)
In-Reply-To: Your message of "Fri, 02 Mar 0900 13:10:20." <20010302041054.71949199EB@mail.cse.psu.edu>

> Anyway, I've not tested 'patch', because I thought it's obvious from the
> header lines of the file...  

All `patch'es at hand (GNU, SunOS, NetBSD ones) doesn't
recognise tcslib.diff as a patch file.  Is there a way
to process `diff -r' output as a patch file on Plan 9
or unix?  I tried something like;
	% patch -p < tcslib.diff
in vain.

> If patch doesn't work, you can do it by hand. ^_^

Yeah, I though of that first too.  But I'm a lazy slug
and don't like the idea that I type codes which have
been already typed.
-- 
Namaarie


  reply	other threads:[~2001-03-02  5:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-02  4:10 okamoto
2001-03-02  5:13 ` YAMANASHI Takeshi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-02  2:48 YAMANASHI Takeshi

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=16342.983509997@beat.cc.titech.ac.jp \
    --to=uncover@campus.cc.titech.ac.jp \
    --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).