From: hiro <23hiro@googlemail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] pull in 9vx
Date: Thu, 3 Jul 2008 14:59:00 +0200 [thread overview]
Message-ID: <f4d8fa40807030559h57919794u854fb8fd5a5ce2d5@mail.gmail.com> (raw)
In-Reply-To: <20080703090012.GB3710@secousse.ipgp.jussieu.fr>
> Besides, I guess others will simply try the simple and dummy
> workaround, as I did, which is to do it as root/with sudo.
> You'll still get the "extended header keyword" message, which doesn't
> seem that bad, but the unpacking will work, as far as I can tell.
>
> Mathieu.
some hospitality at this point would be good for not frightening off
these people searching for sanity...
next prev parent reply other threads:[~2008-07-03 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 18:09 Russ Cox
2008-07-02 20:12 ` [9fans] " hiro
2008-07-02 20:40 ` Charles Forsyth
2008-07-02 21:16 ` hiro
2008-07-03 1:02 ` David Boswell
2008-07-03 1:03 ` Fazlul Shahriar
2008-07-03 1:11 ` hiro
2008-07-03 4:00 ` Russ Cox
2008-07-03 8:46 ` Fernan Bolando
2008-07-03 9:00 ` lejatorn
2008-07-03 12:59 ` hiro [this message]
2008-07-03 13:06 ` erik quanstrom
2008-07-09 17:01 ` andrey mirtchovski
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=f4d8fa40807030559h57919794u854fb8fd5a5ce2d5@mail.gmail.com \
--to=23hiro@googlemail.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).