From: Michael Renzmann <lartc@nospam.otaku42.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: [ANNOUCE] iproute2 update
Date: Wed, 09 Jun 2004 05:00:06 +0000 [thread overview]
Message-ID: <40C69956.6070506@otaku42.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0406081826450.20838-100000@bawx.pilosoft.com>
Hi.
Andreas Klauer wrote:
> Interesting questions - would it break scripts, or fix them? How many
> people did actually check wether k stands for 1024 or 1000 when writing
> their scripts?
I did.
Bye, Mike
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-09 5:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 22:32 [LARTC] Re: [ANNOUCE] iproute2 update alex
2004-06-08 22:42 ` alex
2004-06-08 23:31 ` Stephen Hemminger
2004-06-09 0:31 ` Andreas Klauer
2004-06-09 5:00 ` Michael Renzmann [this message]
2004-06-09 16:38 ` Federico Figueroa C.
2004-06-09 17:16 ` Jose Luis Domingo Lopez
2004-06-09 17:48 ` ThE LinuX_KiD
2004-06-09 19:21 ` Stef Coene
2004-06-09 19:56 ` pf.vd.vlugt
2004-06-09 20:37 ` Stephen Hemminger
2004-06-09 23:09 ` Ed Wildgoose
2004-06-10 19:45 ` Stef Coene
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=40C69956.6070506@otaku42.de \
--to=lartc@nospam.otaku42.de \
--cc=lartc@vger.kernel.org \
/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