Agreed, but I also agree that the error on split ranges is a good simplification to get an implementation in place, and it also doesn't sound super useful, so it sounds okay to fail to begin with. The other cases are easy to handle, though.
On Wed, Aug 6, 2014 at 8:26 AM, Kapil Thangavelu <[email protected]> wrote: > agreed. to be clear .. imo, close-port shouldn't error unless there's a type > mismatch on inputs. ie none of the posited scenarios in this thread should > result in an error. > -k > > > > On Tue, Aug 5, 2014 at 8:34 PM, Gustavo Niemeyer <[email protected]> > wrote: >> >> On Tue, Aug 5, 2014 at 4:18 PM, roger peppe <[email protected]> wrote: >> > close ports 80-110 -> error (mismatched port range?) >> >> I'd expect ports to be closed here, and also on 0-65536. >> >> >> gustavo @ http://niemeyer.net >> >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev > > > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > -- gustavo @ http://niemeyer.net -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
