From: erik quanstrom <quanstro@coraid.com>
To: lucio@proxima.alt.za, 9fans@cse.psu.edu
Subject: Re: [9fans] let's talk contrib
Date: Sat, 28 Apr 2007 21:11:18 -0400 [thread overview]
Message-ID: <ad639274640f6dfb67830e4b34f97b2d@coraid.com> (raw)
In-Reply-To: <154bd45164147842b26c7ba30e3a38ff@proxima.alt.za>
On Sat Apr 28 14:10:31 EDT 2007, lucio@proxima.alt.za wrote:
> > tbz is Lunix, surely.
> > If we value simplicity, contrib should be pre expanded.
> > discuss ?
>
> A valid point, specially when Venti lies behind it.
venti doesn't do compression.
an uncompressed tar is still somewhat foreign to plan 9.
a mkfs archive would be a little closer to home.
but why archive? just copy the file tree.
(yes. i know. my contrib area is filled with compressed tarballs.
old habits die hard. bad habits die harder. old, bad habits. ...
i need a beer.)
- erik
next prev parent reply other threads:[~2007-04-29 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 18:03 mattmobile
2007-04-28 18:10 ` Lucio De Re
2007-04-29 1:11 ` erik quanstrom [this message]
2007-04-29 2:07 ` Federico Benavento
2007-04-29 2:37 ` [9fans] " Darren Bane
2007-04-29 20:10 ` [9fans] " Russ Cox
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=ad639274640f6dfb67830e4b34f97b2d@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
--cc=lucio@proxima.alt.za \
/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).