From: Lucio De Re <lucio@proxima.alt.za>
To: mattmobile@proweb.co.uk, 9fans@cse.psu.edu
Subject: Re: [9fans] let's talk contrib
Date: Sat, 28 Apr 2007 20:10:31 +0200 [thread overview]
Message-ID: <154bd45164147842b26c7ba30e3a38ff@proxima.alt.za> (raw)
In-Reply-To: <QmTs0g3mgRf1.FLNGF5Zl@smtp.o2.co.uk>
> tbz is Lunix, surely.
> If we value simplicity, contrib should be pre expanded.
> discuss ?
A valid point, specially when Venti lies behind it. But 'Net
bandwith/volumes also count. Unfortunately, there is no easy way to
add compression to "cp", specially when running off a remote
filesystem. On the other hand, given that cpu connections are
encrypted (I forget what is the case about remote file system
connections), maybe filesystem connections can be run over TLS
_with_compression_.
Why does that make me think of SSH-2?
++L
next prev parent reply other threads:[~2007-04-28 18:10 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 [this message]
2007-04-29 1:11 ` erik quanstrom
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=154bd45164147842b26c7ba30e3a38ff@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
--cc=mattmobile@proweb.co.uk \
/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).