IETF Logo Mail Archive

Re: [Rfc-markdown] [xml2rfc] Is the --v3 switch still needed?

Tim Wicinski <tjw.ietf@gmail.com> Sun, 24 October 2021 20:36 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88B3F3A083C; Sun, 24 Oct 2021 13:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VDc5CZ25Ey4t; Sun, 24 Oct 2021 13:36:14 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705293A0805; Sun, 24 Oct 2021 13:35:42 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id j9so4729428lfu.7; Sun, 24 Oct 2021 13:35:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MRqBbYocihLaUKai6ZRTxoiBNvfBGEGMmYuvMKLRmmo=; b=LTa64XINLGHecxkj26wFwnqbnRUr6iFJ9lea8jgQFnC3ZsPGddWdzmC+PikfAlGifb fNFKgG0iC11VTAfaUoEuCXG088Off14fO5FDapRGsgvw3P0VaaiV3oiIXQD4SE/Lc3NY lJnYWza/qoJMVlWBW6HUFLEpozkaJltLQGMX0srLkUAE+/eE67GlQLw6QVnlv5dRSuIp b4EaOBT2giDXHahnenjqbNAxfa0YhkFFPpoZ/8rma0DUKR5fEfZv+GQsbKfXIc2E/kM3 8EhGE6tcANjC4HvM4EtYp99BxbRZ3bD9rhaMZQEicMs+KINefbP9/Ryjw7uFQbEp8qGh 7NUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MRqBbYocihLaUKai6ZRTxoiBNvfBGEGMmYuvMKLRmmo=; b=APzhH4Rq7Ee1fPEZa/GA84kRgMFK8srXzc/deUBIVt5LAbJwXQnWit3M8pMw77ipgN QDS/guUQLOwx6APffTy/5zxKWBCVLSbaf2bPPLz5V7UsFfkgwaDdHilQkfOo2J/t9f9t +KlbvKuvV6TqySZ9ZjIHdY5M4WMDE9ZBCYNlqArAF1obXvkIEc5ADYDISfCfUdmsHLzs WsK+fjhHc5QVJQ7KneJuNJ7GkHSuA9u6pyS/MyVlLiXb9xDytmIY7RtMdnUneFBiUdef rb9SCSyjrcZbJ83i+3aGN6P3UVbrm4450ZCWLGFHePbGTcIxqfp+imo2KlXUbqMea3Ez yEoA==
X-Gm-Message-State: AOAM5317HqdvscwtZaGPe5XnYwxQ/uw9NX9Ht7H47uyLNbfNVj5hySTT IsxWqTCoNXzQzP1rHGUMFZxu+2D1HNqBd5RG+54=
X-Google-Smtp-Source: ABdhPJwjU7qcXz+QGSnZt+Xv317SKdj5VM3bhaV12/GPP26uCaFwwAjOSu/RoHmuFP7i/iyUu25sbirDbNXYW908AmA=
X-Received: by 2002:a05:6512:39c7:: with SMTP id k7mr13075200lfu.571.1635107738234; Sun, 24 Oct 2021 13:35:38 -0700 (PDT)
MIME-Version: 1.0
References: <ab61777c-5446-c7c8-1ba1-ec8d8bde2cd4@htt-consult.com> <2A985F36-1332-497F-8DDC-2531245FA8A3@tzi.org> <CADyWQ+FQLoK047A=34VdayGu0s4Q9pnL0FnXkcFs=uAbpcH-Zg@mail.gmail.com> <17adc707-6d65-3455-7fb0-ae82d88e0b77@htt-consult.com>
In-Reply-To: <17adc707-6d65-3455-7fb0-ae82d88e0b77@htt-consult.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Sun, 24 Oct 2021 16:35:27 -0400
Message-ID: <CADyWQ+G0kbe27wN=p4Zjx4VJFZS7889ytfkos+DjZ19AbccbDg@mail.gmail.com>
To: Robert Moskowitz <rgm@htt-consult.com>
Cc: rfc-markdown@ietf.org, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e832c405cf1f2f5c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/S5nR52tqIOLHGdewzzCzKYntv0Q>
Subject: Re: [Rfc-markdown] [xml2rfc] Is the --v3 switch still needed?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Oct 2021 20:36:19 -0000

On Sun, Oct 24, 2021 at 3:39 PM Robert Moskowitz <rgm@htt-consult.com>
wrote:

> I am on ver 3.10.0, but like how do you know that the proper txt was built
> and not some fall back to whatever v2 would do?
>
> Perhaps mv what I did with --v3 to a different name, run without the
> option and use rfcdiff to compare the two txt files?
>
>
I tested it just as you said and my files were identical.

Your Mileage, etc etc


tim

v2.8.7 | Report a Bug | By Email