From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: patch/list sorry/proc-mtime
Date: Thu, 30 Mar 2006 18:37:40 +0200 [thread overview]
Message-ID: <a5bf43e455bb472944e110af133f57bf@lsub.org> (raw)
: In the end everything is matter of convenience and taste, but this
: criticism comming from the person that instigated the tar -z
: abomination is harder to take seriously.
I use tar z a lot.
Why don't you write some code and relax?
Sorry to be so rude.
next reply other threads:[~2006-03-30 16:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 16:37 Fco. J. Ballesteros [this message]
[not found] <dfb566242e58a31d6d4f97b379b4f487@plan9.bell-labs.com>
2006-03-29 23:07 ` uriel
2006-03-29 23:34 ` Russ Cox
2006-03-30 0:13 ` quanstro
2006-03-29 23:34 ` Federico G. Benavento
2006-03-30 8:31 ` Charles Forsyth
2006-03-30 10:09 ` lucio
2006-03-30 11:33 ` Gabriel Diaz
2006-03-30 13:42 ` Anthony Sorace
2006-03-30 14:17 ` Russ Cox
2006-03-30 14:52 ` Gorka guardiola
2006-03-30 16:22 ` uriel
2006-03-30 16:50 ` matt
2006-03-30 17:19 ` Russ Cox
2006-03-31 10:52 ` matt
2006-03-30 17:24 ` rog
2006-03-30 17:32 ` uriel
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=a5bf43e455bb472944e110af133f57bf@lsub.org \
--to=nemo@lsub.org \
--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).