Re: [ietf-types] Status of application/patch or text/patch?
Simon Josefsson <simon@josefsson.org> Thu, 19 July 2012 12:12 UTC
Return-Path: <simon@josefsson.org>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0449321F8769 for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 05:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.909
X-Spam-Level:
X-Spam-Status: No, score=-99.909 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKM2VnVBJfXM for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 05:12:04 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id 1312C21F8759 for <ietf-types@ietf.org>; Thu, 19 Jul 2012 05:12:03 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6JCClLw018806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 19 Jul 2012 14:12:48 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Jon Moore <jonm@jjmoore.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120719:jonm@jjmoore.net::BfGgYWGnf+5je7QQ:ZkIZ
X-Hashcash: 1:22:120719:ietf-types@ietf.org::nfS914lVuwPRpz8S:iW63
Date: Thu, 19 Jul 2012 14:12:46 +0200
In-Reply-To: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> (Jon Moore's message of "Tue, 10 Jul 2012 21:12:22 -0400")
Message-ID: <87k3y03q69.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 12:12:05 -0000
Jon Moore <jonm@jjmoore.net> writes: > Hi folks, > > Given the recent arrival of HTTP PATCH in RFC 5789[1], it seems like > registering a media type for the output of the 'diff' utility would be > a good idea. I found this thread from 2007 where Julian Reschke > proposed this exact thing: > > http://www.ietf.org/mail-archive/web/ietf-types/current/msg00591.html > > Does anyone know where this landed? I'd like to pick up the torch and > at least work on text/diff (using the unified diff format, and limited > to those diffs that can be rendered as valid text/* types). I've > started putting together an Internet Draft for it, but was wondering > if this had actually run into technical trouble, or if it just ran out > of steam in 2007. The issue of how to deal with different character encodings were unresolved, and I think it is important to get right. The approach to specify an application/patch is the easy way out. Trying to resolve it for a text/patch may be possible, but I fear it will be problematic in practice. Thus I lean towards a application/patch. /Simon
- [ietf-types] Status of application/patch or text/… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Julian Reschke
- Re: [ietf-types] Status of application/patch or t… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Simon Josefsson
- Re: [ietf-types] Status of application/patch or t… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Simon Josefsson
- Re: [ietf-types] Status of application/patch or t… Steve Allen
- Re: [ietf-types] Status of application/patch or t… Julian Reschke
- Re: [ietf-types] Status of application/patch or t… Simon Josefsson
- Re: [ietf-types] Status of application/patch or t… Julian Reschke
- Re: [ietf-types] Status of application/patch or t… Bjoern Hoehrmann
- Re: [ietf-types] Status of application/patch or t… Julian Reschke
- Re: [ietf-types] Status of application/patch or t… Bjoern Hoehrmann
- Re: [ietf-types] Status of application/patch or t… Eric Prud'hommeaux
- Re: [ietf-types] Status of application/patch or t… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Paul Libbrecht
- Re: [ietf-types] Status of application/patch or t… Eric Prud'hommeaux
- Re: [ietf-types] Status of application/patch or t… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Paul Libbrecht
- Re: [ietf-types] Status of application/patch or t… Martin J. Dürst
- Re: [ietf-types] Status of application/patch or t… Eric Prud'hommeaux