IETF Logo Mail Archive

Re: [rfc-i] [Tools-discuss] missing line ends in generated TXT (from datatracker)

Robert Sparks <rjsparks@nostrum.com> Thu, 07 November 2019 20:58 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3871209BE for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 7 Nov 2019 12:58:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.75
X-Spam-Level:
X-Spam-Status: No, score=-4.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 QTCZRgq50WdV for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 7 Nov 2019 12:57:58 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85E42120971 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 7 Nov 2019 12:57:58 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8D7F1F4073F; Thu, 7 Nov 2019 12:57:38 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 9CE98F4073F for <rfc-interest@rfc-editor.org>; Thu, 7 Nov 2019 12:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XaLuhX0JsIM for <rfc-interest@rfc-editor.org>; Thu, 7 Nov 2019 12:57:36 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by rfc-editor.org (Postfix) with ESMTPS id 5916CF4073D for <rfc-interest@rfc-editor.org>; Thu, 7 Nov 2019 12:57:36 -0800 (PST)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id xA7Kv2cR022502 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 7 Nov 2019 14:57:03 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1573160224; bh=R8QJUaqQl+Pbe2gKQJczBdnUDkgXLSUng5/UB8t6O1w=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=ogW0WXkS/JsCQ9jBGnrC+SLSkIovWWS/fkL5JoUF7z9y9l2vila0pwpoXAALWSyAR rZl9DRosFMVpM9GNZe680GFKqik+T4IfaHE/OXeOp30RHph2MdyoT3O7z443pnToOQ 02VuAH7fHk9jJj0h7WGdN/n5j/2Kr+74zhw81SKo=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Julian Reschke <julian.reschke@gmx.de>, Dave Rice <dave@dericed.com>
References: <20285.1568652805@localhost> <705AA16B-68B1-4B5E-AE47-0714F6781C1A@dericed.com> <26105.1568818137@localhost> <E70CD0FF-0294-47E5-873F-5E184A248577@dericed.com> <1268.1568828850@localhost> <B4047303-E2B9-4B9D-B368-2ACC85A06D15@dericed.com> <15814.1569013442@localhost> <3a8f5865-9f5c-8c65-63be-bca31c5f1c86@levkowetz.com> <3650B5EF-A442-4291-928A-2FCB2144134C@dericed.com> <06122b6d-d5f9-30b9-2db4-a2427d299a1f@levkowetz.com> <CB32A50B-D6F2-41C4-8AC7-750E35F4941D@dericed.com> <97e68838-ac0c-25e4-67a9-a2a998b6e8af@gmx.de> <3ef6a53c-e18a-9fc7-8324-67f388acd32f@gmx.de> <60a9d29f-03ef-5842-0c21-6930293759da@gmx.de> <cf651c95-9a22-775e-16d9-ebfdc9ee6ed0@gmx.de>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <730f143a-f751-e367-22ad-f1fbf53b1c5a@nostrum.com>
Date: Thu, 07 Nov 2019 14:57:02 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <cf651c95-9a22-775e-16d9-ebfdc9ee6ed0@gmx.de>
Content-Language: en-US
Subject: Re: [rfc-i] [Tools-discuss] missing line ends in generated TXT (from datatracker)
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfc-interest <rfc-interest@rfc-editor.org>, tools-discuss@ietf.org
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 11/7/19 2:50 PM, Julian Reschke wrote:
> On 07.11.2019 21:05, Robert Sparks wrote:
>> Julian -
>>
>> I think that in the Project Manager role (particularly its priority
>> management aspect), I'm "who's in charge" for the question you ask.
>>
>> The update I can give you on this particular ticket is that it has been
>> on the radar, but hasn't been higher priority than many of the immediate
>> changes needed by the RPC as we first took v3 into production.
>>
>> The rate of such changes is slowing (but only a little), and the nature
>> of them are such that I think this particular issue will likely make the
>> top of the stack within the next few weeks (remember there is an IETF
>> meeting in that time).
>>
>> Visibility into the full set of issues and prioritization is less than I
>> would like - many issues were reported and addressed through direct
>> communication between the RPC and Henrik, and I feel that was the right
>> way to handle them given the nature of the cut-over. As the rate is
>> becoming more sane, I expect we'll see increased use of the ticketing
>> system for this set of tools.
>>
>> RjS
>> ...
>
> Robert,
>
> thanks for the update.
>
> It's indeed the lack of information that was bugging me mainly. So maybe
> we need a ticket system for datatracker? 

You meant the v3 format tools perhaps?

(The datatracker's ticket system entry point is at 
https://trac.tools.ietf.org/tools/ietfdb/newticket.)

> Or is there one that I should
> have used?
You had already entered this at 
<https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/444>, so I'm not 
sure what your question is?
>
> Best regards, Julian
>
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
>
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
>
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email