All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: linux-ppp@vger.kernel.org
Subject: Re: patches past 2.4.5
Date: Thu, 28 Nov 2013 19:41:52 +0000	[thread overview]
Message-ID: <8060.1385667712@sandelman.ca> (raw)
In-Reply-To: <858.1385656070@sandelman.ca>


Charlie Brady <charlieb-linux-ppp@budge.apana.org.au> wrote:
    > On Thu, 28 Nov 2013, Michael Richardson wrote:

    >> RADIUS plugin changes:
    > ...
    >> 8) if we find an invalid option in radius config file, it is fatal

    > This one is stupid. I recently sent you a patch to revert it. pppd
    > should not die just because a new option which the radius plugin
    > doesn't care about has been added to the radiusclient. Is the radius
    > plugin reading the config file to validate it for correctness, or to
    > read a few items which it cares about?

Like I said, it might well be that some of the things I saw were not in fact
"features", but regressions.  This one also seemed daft to me, and I haven't
yet found reasons for a bunch of other things.  I.e. does this fix a real
customer problem? 

I think this is an example of this.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	


      parent reply	other threads:[~2013-11-28 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 16:27 patches past 2.4.5 Michael Richardson
2013-11-28 16:40 ` Charlie Brady
2013-11-28 19:41 ` Michael Richardson [this message]

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=8060.1385667712@sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=linux-ppp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.