IETF Logo Mail Archive

Re: [media-types] Mime type for patch files?

Julian Reschke <julian.reschke@gmx.de> Wed, 30 October 2019 06:41 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 761DF12008F for <media-types@ietfa.amsl.com>; Tue, 29 Oct 2019 23:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 (1024-bit key) header.d=gmx.net
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 SIVwewZBJyJz for <media-types@ietfa.amsl.com>; Tue, 29 Oct 2019 23:41:40 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 5A332120043 for <media-types@ietf.org>; Tue, 29 Oct 2019 23:41:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1572417692; bh=HArsEufoRFul0W7vqmtkkbZ3lwpdON3R98r2PMbtxoE=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=RKDJRgHL/WzQRX0ruomMoVo6PXQohvLWDdw5nNMa7na+/rnYLf49tJgm0jkB/iwkr C1RJczNpdpqy9aIEB5nwYtAgi1VwI9oMHhPrw9LcSgp/DyS0xXbAzDvtzQuDtr+wPI tJbL1WU4WoJ08WCoVpAuB8lnS5hesWHV6u+cy7ZE=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.139.155]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1Mv31c-1i8JJL3U1Y-00r32r; Wed, 30 Oct 2019 07:41:31 +0100
To: Mitar <mmitar@gmail.com>, Petter Reinholdtsen <pere@hungry.com>
Cc: media-types@ietf.org
References: <sa67ehyzo3s.fsf@meta.reinholdtsen.name> <20181031102655.GI17721@w3.org> <c419db69-9677-3467-c777-7758450a55fd@henke37.cjb.net> <CANfjZH1COMnjN9jAJGssneP9JymWdo-YmUq93RWu6MxEzBQcEw@mail.gmail.com> <sa6h8gvw48g.fsf@meta.reinholdtsen.name> <sa6lfwuijgh.fsf@meta.reinholdtsen.name> <CAKLmikMdWZF87zusg5td8bmn3uhY1h6XpXDjdN0-DR8VR+ANZA@mail.gmail.com> <sa6bltznv40.fsf@hjemme.reinholdtsen.name> <CAKLmikOPT6O7K5+1iXM_Jw+xyFUv8KKT-BVawEJRgnX_rVxdWw@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <edc29427-59c8-cbb4-ae39-904840423237@gmx.de>
Date: Wed, 30 Oct 2019 07:41:25 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAKLmikOPT6O7K5+1iXM_Jw+xyFUv8KKT-BVawEJRgnX_rVxdWw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:CDXkdSb/+rh+umLadcv0vVbCGRgeGgMOMTKMWUOB1b16MSQMi2X oVGaflcUL2y426eeXlPI4QoCR16VnoXg+DRct8pLZMsHUhCwd2k2x3PRBnP1Hbrlq94p4UR N5gy9x4DsvxgpDKFm6PGN07O/RPx0n7YQwMzYzJPdjx+xAhdMqj1Q6Wi4RsmZnzMdJFfOrh PDLooveLMslC/jkoVO/Kw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:H7IxtDOJ0J0=:rJeUfdjnY/1XEoh6TTl5Oi 8ayWiYlyvomduSVWNgIh0mZSS979S4FnIZjJL3kzAj9QmhfTip/LG55WAMSnP28wphpj+vU2/ dJYGHvS9ljreevAtJc0tJ4JnfDdYdxoVB40Epbf9hAFsb5WbCAmh/dIa7bRoiSprIJIwCGSoR EaMzVnEhZxhTMoxdWGMwUGSTGtFSTTAnsLr5daDEfbv/AWmsQF1wqHWohawbc7LUEHnyhjqgg Zcq14aHH4z1T5VDS79KNp74KhopKl9RbdLgtQ8JEvuSj6PC6G7/yRUD0eD8//Wfh/4BUnd25B ZMZmPdH4/Mz0WvAPhojLrCmoaKuozAq2cWSV4YRNuzaRFhV8qwUvVasZC2+8dP1qAJhSQVNV/ wLVjUbZo5trOMqg17N+DLzTCaXOPf3DmEyc7pQt/9sRq/7u1ZStuaWdTCi21V3HEP/7SiPjH8 EkDwV67jZkczn54DOpfah+Qf66AIrldH3HEgn+WDRj4WLUjdMk64wITkM+f6lXLdY5IaKK51w ASJQqKV5C+wVGoTPkDWeEUbFn8arss9ZtnmqBtleHrDWgxy/2kU0DX53alB8U7aYZETFyF5c1 k31SchI3eweBi0Ph2iVAC66WbuXIZDtnotpFAD1AuFE8XbitUfcgN4qoc+l+1a8lgi1bskLmZ wWXIvi5PO2ivFQkq6iruQx0if6BWObdfT4QdvlhNaa1WPLhXcXOk6VJZ7Jf0QIT2d9+NyTxix pnHdquVWMrPYgZq3yy3/gEtNpJQI2EQYRGjQGr6QN2T1zVg/X/nvuHF53isa2FC5xbf0sqV5I 1ac9MYxQc5UKXtWBsH34BUT7gCscxC2rLLcwjO4yqlCgVNpgsHYkVeuoN6itfj0ZizQQuGzNb gBIKfGkjPPFk3nnOKEtFO5eu4sT+y8ajBMt5g3Ldtjm2Lr861mHeSH52InPxYZdqyFtZgK+u1 VR89ymtMa2sDi+cnHO1EkAqnmmTOmfkYAzp//xY3r/ULMpFn/1uy12CoQ/jkdMQJ/lOeocep+ 1njQ0bMOk9gklDYKZxay6IBmoHfL76ELqz80bjXcVa9AgVjTSUMO3U/pKzGJk6MN9dSrJvvS8 zjeRdkoSucBAuixy6zGppbPZif1apprukWK0yUrMgcIzFTInDFIuWAWIOOKCr00zXVnbhFlAI n3gPVKjHn2SDsf33ozuwQfNMyLwUEFc721uPDj91h6igM6egrWU9zxlNZhnaRSn4rt8fNGM3x Je/lyd7I2C2CCnash+jL6bi+LxAyX5IQr5ZOMtfKhDmAGX/aJNKQabGYFMOw=
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/PjRd8cqlLDTHoW7RLz7HhPrZwwA>
Subject: Re: [media-types] Mime type for patch files?
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2019 06:41:43 -0000

On 30.10.2019 01:38, Mitar wrote:
> Hi!
>
> On Tue, Oct 29, 2019 at 1:40 PM Petter Reinholdtsen <pere@hungry.com> wrote:
>> Aha.  Where can we see what you submitted?
>
> I do not think it is public. :-( Or at least I do not know how to access it.
>
>> I do not believe I have seen
>> that MIME type used for diffs anywhere.  Where is it used?
>
> Yes, it is a brand new. Because if we want to standardize it, we
> should use a standard tree. We cannot just standardize a private one
> (especially because they all use obsolete x- prefix).
>
> Now, I picked a standard tree and not vendor tree even if there is no
> official standard associated with it, and I hope it will go through
> and that some IETF working group will approve it. Otherwise we will
> have to resubmit it as text/vnd.unified-diff which looks not as nice,
> especially for something so common as unified diff.
> ...

Well, what exactly did you submit? If it's supposed to be in the
standards tree, it should come with a pointer to a specification...

Best regards, Julian

v2.23.0 | Report a Bug | By Email