Robert Wilton rwil...@cisco.com wrote:
Hi Martin,
On 20/08/2015 09:15, Martin Bjorklund wrote:
Andy Bierman a...@yumaworks.com wrote:
On Wed, Aug 19, 2015 at 4:25 AM, Martin Bjorklund m...@tail-f.com
wrote:
Robert Wilton rwil...@cisco.com wrote:
On 18/08/2015 18:22, Andy Bierman
On Fri, Aug 21, 2015 at 6:01 AM, Martin Bjorklund m...@tail-f.com wrote:
Robert Wilton rwil...@cisco.com wrote:
Hi Martin,
On 20/08/2015 09:15, Martin Bjorklund wrote:
Andy Bierman a...@yumaworks.com wrote:
On Wed, Aug 19, 2015 at 4:25 AM, Martin Bjorklund m...@tail-f.com
wrote:
On 21 Aug 2015, at 15:01, Martin Bjorklund m...@tail-f.com wrote:
Robert Wilton rwil...@cisco.com wrote:
Hi Martin,
On 20/08/2015 09:15, Martin Bjorklund wrote:
Andy Bierman a...@yumaworks.com wrote:
On Wed, Aug 19, 2015 at 4:25 AM, Martin Bjorklund m...@tail-f.com
wrote:
Robert
Hello
I'm dealing with issue where one yang module includes many yang submodules.
My question is if one of submodules gets updated with newer revision than
parent module,
does parent module needs to be updated too?
Is this mandatory?
If parent module doesn't get updated, can we consider this as
Hi Martin,
On 20/08/2015 09:15, Martin Bjorklund wrote:
Andy Bierman a...@yumaworks.com wrote:
On Wed, Aug 19, 2015 at 4:25 AM, Martin Bjorklund m...@tail-f.com wrote:
Robert Wilton rwil...@cisco.com wrote:
On 18/08/2015 18:22, Andy Bierman wrote:
This is how languages like SMIv2 and YANG
Ladislav Lhotka lho...@nic.cz wrote:
Hi,
YANG 1.1 will allow 'choice' under 'choice (see issue Y29), but is there
any reason for not allowing 'uses' under 'choice'?
If you have a grouping with N nodes (N 1), expanding in directly
under a choice would create N cases. Probably not what you
