From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Correct 'change' behaviour
Date: Tue, 03 Nov 2015 14:14:22 +0100 [thread overview]
Message-ID: <87k2pzns29.fsf@toke.dk> (raw)
In-Reply-To: <5638B29D.9020503@darbyshire-bryant.me.uk> (Kevin Darbyshire-Bryant's message of "Tue, 3 Nov 2015 13:11:57 +0000")
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
> Interestingly I think the opposite. On a change parameters should be
> left alone unless they're the thing I'm changing. It's a 'change' to
> an instantiation, *not* an instantiation if you get my drift.
Yes, that is indeed implied in the 'change' verb. However, the tc verb
is 'replace'. If we go with the "leave things alone" paradigm, there
will need to be some way to explicitly specify defaults...
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-11-03 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 12:59 Toke Høiland-Jørgensen
2015-11-03 13:11 ` Kevin Darbyshire-Bryant
2015-11-03 13:14 ` Toke Høiland-Jørgensen [this message]
2015-11-03 17:24 ` Jonathan Morton
[not found] ` <87oafbat54.fsf@toke.dk>
2015-11-03 17:32 ` Jonathan Morton
2015-11-03 17:51 ` Toke Høiland-Jørgensen
2015-11-03 19:07 ` Toke Høiland-Jørgensen
2015-11-03 19:14 ` Dave Taht
2015-11-04 11:09 ` Toke Høiland-Jørgensen
2015-11-04 14:28 ` Sebastian Moeller
2015-11-04 18:04 ` Kevin Darbyshire-Bryant
2015-11-04 18:51 ` Toke Høiland-Jørgensen
2015-11-04 18:55 ` Sebastian Moeller
2015-11-03 17:54 ` Kevin Darbyshire-Bryant
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2pzns29.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.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