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

Petter Reinholdtsen <pere@hungry.com> Wed, 30 October 2019 08:30 UTC

Return-Path: <pere@hungry.com>
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 CE9D11200C4 for <media-types@ietfa.amsl.com>; Wed, 30 Oct 2019 01:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 RdGMBWWABPFW for <media-types@ietfa.amsl.com>; Wed, 30 Oct 2019 01:30:10 -0700 (PDT)
Received: from bouvier.getmail.no (bouvier.getmail.no [84.210.184.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 411B21200B5 for <media-types@ietf.org>; Wed, 30 Oct 2019 01:30:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id 087E9402A8; Wed, 30 Oct 2019 09:30:03 +0100 (CET)
Received: from bouvier.getmail.no ([127.0.0.1]) by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id ePf2NohATi5I; Wed, 30 Oct 2019 09:29:52 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id BA35340359; Wed, 30 Oct 2019 09:29:52 +0100 (CET)
X-Virus-Scanned: amavisd-new at bouvier.get.c.bitbit.net
Received: from bouvier.getmail.no ([127.0.0.1]) by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id vjMp-2qJLtgz; Wed, 30 Oct 2019 09:29:52 +0100 (CET)
Received: from hjemme.reinholdtsen.name (cm-84.212.214.101.getinternet.no [84.212.214.101]) by bouvier.getmail.no (Postfix) with SMTP id 8CAE8402A8; Wed, 30 Oct 2019 09:29:52 +0100 (CET)
Received: (nullmailer pid 1691 invoked by uid 10001); Wed, 30 Oct 2019 08:29:51 -0000
From: Petter Reinholdtsen <pere@hungry.com>
To: Mitar <mmitar@gmail.com>
Cc: media-types@ietf.org
In-Reply-To: <CAKLmikOPT6O7K5+1iXM_Jw+xyFUv8KKT-BVawEJRgnX_rVxdWw@mail.gmail.com>
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>
Date: Wed, 30 Oct 2019 09:29:51 +0100
Message-ID: <sa6r22upreo.fsf@hjemme.reinholdtsen.name>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/1Oh2WOrY8dZx_jKUULGIL6-TNFY>
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 08:30:12 -0000

[Mitar]
> I do not think it is public. :-( Or at least I do not know how to
> access it.

Well, can you make the text you submitted public?  For example by
posting it here?  If that is impossible, what about using
<URL: https://0bin.net/ > or some other pastebin service, if you have no
better suggestion.

> 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).

The currently used ones are or text/x-diff (most popular) and
text/x-patch.  Would it be impossible to register the first one based on
historic usage?

-- 
Happy hacking
Petter Reinholdtsen