From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] dup(3)
Date: Fri, 16 Oct 2009 18:25:58 +0100 [thread overview]
Message-ID: <f8d5169993223c89e8453da0d44788f4@quintile.net> (raw)
In-Reply-To: <138575260910160858nfc9444fr73e3328d98eac98a@mail.gmail.com>
> @{builtin cd $1 && tar cf /fd/1 .} | @{builtin cd $2 && tar xTf /fd/0}
the /fd/1 and /fd/0 fererences ensure that dircp will work with ape's tar
which doesn't read/write stdin/stdout by default like plan9's does.
-Steve
next prev parent reply other threads:[~2009-10-16 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 15:58 hugo rivera
2009-10-16 16:52 ` Russ Cox
2009-10-16 17:25 ` Steve Simon [this message]
2009-10-19 9:10 ` hugo rivera
[not found] <<138575260910160858nfc9444fr73e3328d98eac98a@mail.gmail.com>
2009-10-16 16:06 ` erik quanstrom
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=f8d5169993223c89e8453da0d44788f4@quintile.net \
--to=steve@quintile.net \
--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).