netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: ipv6 steaming pile of poo...
Date: Mon, 24 Jan 2011 09:20:43 +1000	[thread overview]
Message-ID: <20110124092043.49b7d34a@s6510> (raw)
In-Reply-To: <20110123.123754.246545770.davem@davemloft.net>

On Sun, 23 Jan 2011 12:37:54 -0800 (PST)
David Miller <davem@davemloft.net> wrote:

> 
> Thanks to the fact that I let a change causing known regressions live
> in the tree for almost a year (don't worry I've learned my lesson):
> 
> From dc2b99f71ef477a31020511876ab4403fb7c4420 Mon Sep 17 00:00:00 2001
> From: stephen hemminger <shemminger@vyatta.com>
> Date: Mon, 8 Feb 2010 19:48:05 +0000
> Subject: [PATCH] IPv6: keep permanent addresses on admin down
> 
> We have over a year of follow-up changes to revert if we want to
> get rid of this turd.
> 
> This means getting rid of all the changes that tried to fix bugs in
> the new ipv6 semantics made by Lorenzo Colitti, and the hlist
> conversions, and all changes dependent upon those.
> 
> But no matter, this has to be done and I don't care if we lost lots
> of cleanups and other work as a result of doing this, it just has to
> be done.
> 
> And this is _why_ we must revert changes causing known regressions
> as soon as they are discovered, not months or a year later.  Because
> after that much time, undoing the damage becomes that much harder.
> 
> So if you folks wonder what I'm working on the next couple of days,
> this is it.
> --

Please post the full set of diffs, to allow for putting the bug fixes
back.

  reply	other threads:[~2011-01-23 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-23 20:37 ipv6 steaming pile of poo David Miller
2011-01-23 23:20 ` Stephen Hemminger [this message]
2011-01-24  4:03   ` David Miller

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=20110124092043.49b7d34a@s6510 \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).