Re: [Tools-discuss] [rfc-i] Recommendation 9 from Results and analysis of the survey of I-D authors on formats and tools

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 07 February 2021 04:31 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F23143A2F77 for <tools-discuss@ietfa.amsl.com>; Sat, 6 Feb 2021 20:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4UdKiH6vXG4 for <tools-discuss@ietfa.amsl.com>; Sat, 6 Feb 2021 20:31:18 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B192E3A2F76 for <tools-discuss@ietf.org>; Sat, 6 Feb 2021 20:31:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C08CA389A9; Sat, 6 Feb 2021 23:34:20 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YeFORskqG7iv; Sat, 6 Feb 2021 23:34:19 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 99D10389A7; Sat, 6 Feb 2021 23:34:19 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4B545C65; Sat, 6 Feb 2021 23:31:14 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, RFC Interest <rfc-interest@rfc-editor.org>, tools-discuss <tools-discuss@ietf.org>
In-Reply-To: <139065E7-F8DF-418D-89E9-156BE35C4DFA@tzi.org>
References: <161240956258.5082.18097054694330751435@ietfa.amsl.com> <CAA=duU1c3g0qmNmSN9jpfq3o4Lggxg_vT3xLdmwxAzLPm0r-iQ@mail.gmail.com> <15878309-55BA-4BE0-BD26-060308BA1270@tzi.org> <E77A02FF-4DF8-4030-BC77-4355A705E00E@adobe.com> <A2CC3D3F-3920-4E51-AAD7-1FFE83CA5ECB@tzi.org> <18192.1612647870@localhost> <CADyWQ+HoVg9H8xKLLoGkatVoDTg60bdNANNADyDWxnBz=cbdWQ@mail.gmail.com> <29774.1612663657@localhost> <139065E7-F8DF-418D-89E9-156BE35C4DFA@tzi.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 06 Feb 2021 23:31:14 -0500
Message-ID: <7618.1612672274@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/iZKaV0n0s4zOxaaIQyORuT35-7o>
Subject: Re: [Tools-discuss] [rfc-i] Recommendation 9 from Results and analysis of the survey of I-D authors on formats and tools
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2021 04:31:21 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    > While there is a bit of redundancy in ...

    > ~~~~
    > <CODE BEGINS> file "ietf-sid-file@2020-02-05.yang"
    > {::include ietf-sid-file@2020-02-05.yang}
    > <CODE ENDS>
    > ~~~~

    > …, I’m not sure avoiding that warrants a Perl script by itself.

Well, it started in XML days.

And there were several yang files, and they got generated/processed with
today's date inserted.  Being sure to use the latest one was error prone at one point.
Edit one, but update the other reference... oops.

And then sid files and tree files.
I could probably submit an "::include-yang" patch to do the right thing, and
maybe I should.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide