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

Petter Reinholdtsen <pere@hungry.com> Thu, 01 November 2018 11:01 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 AD08C1277D2 for <media-types@ietfa.amsl.com>; Thu, 1 Nov 2018 04:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 uXQwyVpji73V for <media-types@ietfa.amsl.com>; Thu, 1 Nov 2018 04:01:22 -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 0B06012777C for <media-types@ietf.org>; Thu, 1 Nov 2018 04:01:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id E698040032; Thu, 1 Nov 2018 12:01:16 +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 c_x2W7zQx6rW; Thu, 1 Nov 2018 12:01:15 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id 833614002F; Thu, 1 Nov 2018 12:01:15 +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 SjMttAl_sQ61; Thu, 1 Nov 2018 12:01:15 +0100 (CET)
Received: from hjemme.reinholdtsen.name (cm-84.212.222.24.getinternet.no [84.212.222.24]) by bouvier.getmail.no (Postfix) with SMTP id 59AE64002E; Thu, 1 Nov 2018 12:01:15 +0100 (CET)
Received: (nullmailer pid 14007 invoked by uid 10001); Thu, 01 Nov 2018 11:01:15 -0000
From: Petter Reinholdtsen <pere@hungry.com>
To: media-types@ietf.org
In-Reply-To: <7a0d47e2-807e-12d3-f6eb-727fd94ddcb1@ladisch.de>
References: <sa67ehyzo3s.fsf@meta.reinholdtsen.name> <20181031102655.GI17721@w3.org> <sa6y3adnvs3.fsf@meta.reinholdtsen.name> <7a0d47e2-807e-12d3-f6eb-727fd94ddcb1@ladisch.de>
Date: Thu, 01 Nov 2018 12:01:15 +0100
Message-ID: <sa636slnjt0.fsf@meta.reinholdtsen.name>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/4t--yoZ7F_eKKjJLEn57oc5eyes>
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: Thu, 01 Nov 2018 11:01:27 -0000

[Clemens Ladisch]
> Pretty much all version control systems can generate patches.  However,
> the default output typcially does not rely on MIME type detection but
> uses custom formatting (in a GUI, or in HTML).  As far as I can see,
> the only place where the MIME type might matter are e-mail
> attachments.

It also matter for downloading from web sites and selecting files in a
Linux/unix file browsers, where the user can get a patch viewer instead
of a text editor. :)

> As it happens, cgit deliberately returns "text/plain" (e.g.,
> <http://git.savannah.gnu.org/cgit/patch.git/patch/?id=HEAD>).

While the Debian source service hand out patches
using 'text/x-diff', as can be seen from
<URL: https://sources.debian.org/data/main/c/conv-tools/20160905-1/debian/patches/autoreconf-buildable.patch >.

There is no doubt that both the mime types are in use, so the question
is really which one to choose as the official one, unless creating a new
one is better.  It will take time for a registered MIME type to gain
tracktion no matter which one we pick, but of course by picking one of
the used ones, we get a head start with existing users. :)

-- 
Happy hacking
Petter Reinholdtsen