Open Stack

If you're including me as a vote for nin, you should also consider me as a vote for not_in. Otherwise, count me as half a vote for either. I still think not_in is just ever-so slightly better than nin. 

-----Original Message-----
From: milanisko k <vetrisko at gmail.com>
Reply: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Date: November 16, 2016 at 02:47:12
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject:  Re: [openstack-dev] [api]

> Guys,
>  
> thanks for the responses, so far we've got (if I'm not mistaken):
>  
> ?state=nin: 3 (including me)
> ?state=not_in: 1
> ?state=out: 0
> ?not_state=in: 0
>  
> I'd like to finish this poll by EOW so that more folks have the opportunity
> to express their preference.
>  
> Cheers,
> milan
>  
>  
> 2016-11-15 13:50 GMT+01:00 Miles Gould :
>  
> > On 14/11/16 20:52, Ian Cordasco wrote:
> >
> >> not_in is nice and explicit while nin and out are a bit, more clever. I
> >> think we should avoid trying to be clever.
> >>
> >
> > Agreed - I think not_in is more intelligible and guessable than the other
> > suggestions.
> >
> > Miles
> >
> >
> > __________________________________________________________________________  
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe  
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> __________________________________________________________________________  
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe  
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>  

--  
Ian Cordasco