IETF Logo Mail Archive

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

Mitar <mmitar@gmail.com> Wed, 30 October 2019 00:39 UTC

Return-Path: <mmitar@gmail.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 4916B120059 for <media-types@ietfa.amsl.com>; Tue, 29 Oct 2019 17:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 Lda8XJ7-IcCw for <media-types@ietfa.amsl.com>; Tue, 29 Oct 2019 17:39:12 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 54286120052 for <media-types@ietf.org>; Tue, 29 Oct 2019 17:39:12 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id a21so622097ljh.9 for <media-types@ietf.org>; Tue, 29 Oct 2019 17:39:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j3wF3fQlNEUmjS1U4TsdXlY+0nrbgTul6DfGnSTGvh8=; b=k8pxIlUInrOVyvdxKiONhCAE1cHfAjwJJHx4OmtvgOgS+bNMaw6jN5t6K9PHhnLpmY /gBBXf8l1ANIYCv8kX3fHymZ+1+GN7e74jaGnN05pVdVb+pLB8Gc+0zJnlmK7SUgQMY7 dhpViHp5CJaFFRG2TEA+ddCvnwNYxzD+8w1pNeKwPUNTqGyqfr5Nl1Akf1hYqFsKz2gX 0QreJHnKHhf4LTmgFK2Fq8N902eb+qlMiz+9dWThqGf5Ssl7jHdRK/jDBbsAlx6/86et FJyn/ZSLqp8SQomXdanF8yPRVbeK1XFynZRDtkONk9CQrKTYyxU9k5byVaXSBz3cSzAT XNmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j3wF3fQlNEUmjS1U4TsdXlY+0nrbgTul6DfGnSTGvh8=; b=dI9FTn783uxmed7W2+749rhvx+2VM8ov5BE4YkLR/sLJHmV6J+LLxO/Yv3N39aZStJ +OPbcuU6Q9JaQNTUa6U/U+9zwJvN5wYW6L9ii+EemPtXQ6mb1HaeFJFMAYpMfLnlE5Qo WHnURG81eyl9RCgYVv7uOiWJ4mHaXZJYwJUU4VtyhEQnAdTS23gsEF7MIokzphLZLR2U EqDFDI+k/Gw3774Y7SVqkEfYK57Xsxpt9JgNy2Eyvy2R3H+CJTT6MjvxiXRPY+6kFpZl 3sArosFJhvwNx3z0skFFIZlUGY4fQbHe4IipWKgSvDLWz+AgP+ko+e5qqsJwDOPdlzwG fkoA==
X-Gm-Message-State: APjAAAUny4tBV8djguDw+ZjrAwCSpiLvIMr44nx5KJoi+bmWvM5nceRR pGvoswLytxvcal3lMAYqpTUaNBNu854Pe8r6iaq9URpH
X-Google-Smtp-Source: APXvYqyd0yUD5mJXygWcXTdde37MFpEzWdHyE/Ag7ullJEEqo2VL+v4DbN/YTTDbeUaV7UfTE3Ozqdyyh3P4IcibsgA=
X-Received: by 2002:a2e:58d:: with SMTP id 135mr4344462ljf.57.1572395950572; Tue, 29 Oct 2019 17:39:10 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <sa6bltznv40.fsf@hjemme.reinholdtsen.name>
From: Mitar <mmitar@gmail.com>
Date: Tue, 29 Oct 2019 17:38:57 -0700
Message-ID: <CAKLmikOPT6O7K5+1iXM_Jw+xyFUv8KKT-BVawEJRgnX_rVxdWw@mail.gmail.com>
To: Petter Reinholdtsen <pere@hungry.com>
Cc: media-types@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/gQUts8Yd0NCVxltZneFLeNFOQV0>
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 00:39:14 -0000

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.


Mitar

-- 
http://mitar.tnode.com/
https://twitter.com/mitar_m

v2.23.0 | Report a Bug | By Email